On booting, independant from the installed version: * /run/lock: correcting owner * Caching service dependencies ... iService 'netmount' needs non existant service 'net'
Created attachment 643522 [details] iwd-1.7 build log
Are you asking for iwd to be listed as a net provider on its own?
(In reply to Ben Kohler from comment #2) > Are you asking for iwd to be listed as a net provider on its own? Sorry, I am unsure about the implications and not really familiar with best practice for init.d files. And I haven't tried iwd together with netmount. But I have tried with "provide net" in iwd's init.d file (seen this in dhcpcd) and openrc seems to be happy. Even if you run iwd together with dhcpcd, both having "provide net", ther is no confusion. It's just a proposal.
I don't currently consider iwd standalone to be a usable net provider, are you using it on its own like that? I believe you have to enable the internal DHCP/IP configuration manually, and there is still no resolv.conf handling that I know of.
(In reply to Ben Kohler from comment #4) > I don't currently consider iwd standalone to be a usable net provider, are > you using it on its own like that? That's exactly what I am doing, as proposed by https://wiki.gentoo.org/wiki/Iwd#iwd_native > > I believe you have to enable the internal DHCP/IP configuration manually, > and there is still no resolv.conf handling that I know of. Is there any need to have such?
(In reply to charles17 from comment #5) > Is there any need to have such? To claim to "provide net", I would lean towards "yes". What are you using to handle resolving, openresolv or systemd or other?
(In reply to Ben Kohler from comment #6) > [...] > What are you using to handle resolving, openresolv or systemd or other? Not any. Isn't it as stated in the wiki "As of version 0.19 iwd contains a DHCP client and can manage routes and DNS resolving."
So it updates your resolv.conf for you? Or what is handling that?
(In reply to Ben Kohler from comment #8) > So it updates your resolv.conf for you? Or what is handling that? Just tested. It doesn't, at least not out of the box. It was still using the existing resolv.conf file.
This is not going to work very well as you move from one network to another
Using something like this in RDEPEND should pull in openresolv if dhcpcd is not installed: resolvconf? ( || ( net-dns/openresolv net-misc/dhcpcd ) )
If it supports resolvconf it should pull in openresolv regardless of dhcpcd - as dhcpcd supports it natively too.
I'm not actively using this kind of setup, but maybe we can add a new USE flag to iwd like "standalone". This flag could ensure that all of the proper deps & settings (iwd/main.conf changes, "provide net" in conf.d/iwd, etc) are added so that iwd can run w/o dhcpcd or NM or other stuff.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=08966208e5ed1f41923e5207e6cbec70b2cd3cb9 commit 08966208e5ed1f41923e5207e6cbec70b2cd3cb9 Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2020-09-03 16:45:29 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2020-09-03 17:37:34 +0000 net-wireless/iwd: revbump to test new standalone mode Bug: https://bugs.gentoo.org/727218 Package-Manager: Portage-3.0.5, Repoman-3.0.1 Signed-off-by: Ben Kohler <bkohler@gentoo.org> net-wireless/iwd/iwd-1.8-r2.ebuild | 179 +++++++++++++++++++++++++++++++++++++ net-wireless/iwd/metadata.xml | 2 + 2 files changed, 181 insertions(+)
Can you test iwd-1.8-r2 with USE=standalone?
(In reply to Ben Kohler from comment #15) > Can you test iwd-1.8-r2 with USE=standalone? Message (comment #0) gone. Seems to work.
Thanks for testing. If you think of some improvements needed for the ebuild checks, please open a new bug.
