Helo, I am using wpa_supplicant at wired network and linux kernel has no wireless compiled in. From version 2.6-r1 wpa_supplicant stopped working. It enabled config option CONFIG_MATCH_IFACE. This is output of running: # /usr/sbin/wpa_supplicant -i eth0 -D wired -c /etc/wpa_supplicant/config.conf -P /run/wpa_supplicant.pid Successfully initialized wpa_supplicant nl80211: 'nl80211' generic netlink not found Failed to initialize driver 'nl80211' There is problem in function "wpa_supplicant_init_match" which wants to use driver nl80211 (first one) to handle interfaces (only when that CONFIG_MATCH_INTERFACE). But this driver is not working as there is no wireless compiled in kernel and wpa_supplicant stops. Config for drivers nl80211, wext and wired are set at ebuild and nl8011 is first used in code so there is no possibility to make that wired driver first one to make it to work (except to modify ebuild or code). emerge --info is nonsense here so not attaching it for now. Pavel Semerad
Sounds like for your use case another USE flag were needed? See https://forums.gentoo.org/viewtopic-t-1036958-start-13.html
Yes, if CONFIG_MATCH_IFACE will be dependent on USE flag, then it will work as before for my use case. Or another USE flags which will disable nl80211 and maybe wext to have wired driver as the first one.
(In reply to Pavel Semerad from comment #0) > [...] > There is problem in function "wpa_supplicant_init_match" which wants to use > driver nl80211 (first one) to handle interfaces (only when that > CONFIG_MATCH_INTERFACE). > But this driver is not working as there is no wireless compiled in kernel > and wpa_supplicant stops. > Config for drivers nl80211, wext and wired are set at ebuild and nl8011 is > first used in code so there is no possibility to make that wired driver > first one to make it to work (except to modify ebuild or code). > [...] Sounds like a source code bug. Adding another USE flag to workaround it isn't a proper solution. Please report upstream (http://lists.infradead.org/pipermail/hostap/) so they can fix it for next version. Don't forget to link your upstream item here.
I can try it report upstream, but it can be considered not as bug but a feature for such combination of CONFIG directives used in ebuild (it can be made working with another CONFIG settings). Someone in gentoo decided that setting CONFIG_MATCH_INTERFACE doesn't broke things (https://forums.gentoo.org/viewtopic-p-7974604.html#8005096) and this isn't true in my use case.
(In reply to Pavel Semerad from comment #4) > I can try it report upstream, but it can be considered not as bug [...] Just try and we'll see their reply.
