Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 669632 - net-misc/networkmanager[iwd] won't find wifi networks if iwd hasn't been started before
Summary: net-misc/networkmanager[iwd] won't find wifi networks if iwd hasn't been star...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Ben Kohler
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-25 20:42 UTC by AE
Modified: 2019-07-28 20:10 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description AE 2018-10-25 20:42:10 UTC
I'm seeing some unwanted behaviour from NetworkManager in conjunction with iwd: If iwd starts after NetworkManager (as might and did happen on a freshly installed, fast laptop), the latter won't pick up the wifi networks iwd finds. Restarting NetworkManager fixes this, and a workaround to avoid it happening in the first place is adding the line 'before net' to the depend() function in '/etc/init.d/iwd'.

Versions:

=net-wireless/iwd-0.10
=net-misc/networkmanager-1.14.4
Comment 1 Ben Kohler gentoo-dev 2018-10-25 20:49:49 UTC
I'm working with upstream on this as we speak to find out why this ordering matters, there may be a bug in iwd or NM itself.  This is happening on systemd boot as well.
Comment 2 David Heidelberg (okias) 2019-01-24 11:48:26 UTC
Any progress? I know that iwd is not yet widely used, but would be nice to have it working without restarting NM everytime.
Comment 3 David Heidelberg (okias) 2019-01-24 11:50:01 UTC
also, still present in


iwd 0.14
networkmanager 1.15.1
Comment 4 AE 2019-05-26 15:52:50 UTC
Bug seems to have been resolved upstream as of openrc-0.42.1 + networkmanager-1.16.0 + iwd-0.18
Comment 5 hfern 2019-07-28 20:10:32 UTC
Starting with version 0.18 iwd is actively managing network interfaces. It will destroy the wireless interfaces detected by (e)udev, and create new ones. The new ones do not comply to predictable network interface naming convention, but will have an 'old fashioned' kernel name like wlan0. See for details here: https://iwd.wiki.kernel.org/interface_lifecycle. 

I could imagine that if NetworkManager starts before iwd, that it will detect an interface named wlp2s0, but then when iwd starts wlp2s0 will be destroyed and a new one called wlan0 will be created.
There seems to commandline and configuration options to prevent iwd from doing this, but I have not got that working.