GNOME Bugzilla – Bug 743701
NM oblivious to wpa_supplicant's INTERFACE_DISABLED state
Last modified: 2020-11-12 14:33:53 UTC
The supplicant changes the interface object's state to INTERFACE_DISABLED when one of two things occurs: 1) the netdev goes !IFF_UP - this is a problem and means that we cannot just move the NMDeviceWiFi to UNAVAILABLE when we get INTERFACE_DISABLED, since it happens when changing the MAC address or for other normal reasons 2) some external process tells the supplicant to forget the interface - like if you run ConnMan or something else alongside NM Since we can't directly use the DISABLED state but still should correctly handle #2, thankfully we can use the InterfaceRemoved signal on the main wpa_supplicant dbus interface. Obviously when we get that signal we should move the NMDeviceWiFi to UNAVAILABLE since something else is touching wifi. I'll work on this, it's not an urgent problem, but instead of just fixing it one-off I'm going to try converting the whole supplicant manager over to GDBus and fix it that way.
if the quick-hack-solution would be simple and correct, it would be useful for easy backporting to nm-1-0 (instead of backporting a major refactoring)...
See bug 744598 for the supplicant GDBus stuff.
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).