On Sep 3, 2015 7:28 AM, "Simon Kitching" <[email protected]> wrote: > > On 09/03/2015 01:21 PM, Hazel Russman wrote: >> >> On Thu, 03 Sep 2015 11:27:08 +0200 >> Simon Kitching<[email protected]> wrote: >> >>> Hi All, >>> >>> I've been struggling with getting wireless working recently - finally >>> working. >>> >>> One of the significant problems is that the BLFS book recommends >>> compiling wpa_supplicant with *two* back-ends enabled: "wext" and >>> "wired". Unfortunately, that means the "-D" option on the commandline is >>> mandatory; if omitted then wpa_supplicant just silently does nothing >>> (without any warning or error messages). >>> >>> And some other files, eg systemd's "wpa_supplicant.service" or dhcpcd's >>> wpa_supplicant hook-script, do not specify a -D option (presumably they >>> assume that only the wext back-end is compiled in). >>> >>> I'm surprised nobody else has had problems with this. Maybe a warning in >>> the BLFS book would be a good idea? >>> >>> Regards, >>> Simon >>> -- >> >> I have just checked on my laptop (lfs-systemd 7.6). ps -ax|grep wpa shows that wpa is running without the -D option. Nevertheless I am online and can ping sites. The supplicant daemon was launched [email protected]. There is no driver option mentioned in the wpa_supplicant.service file either, but wpa_supplicant-wired.service does specify -Dwired. It looks like the book has this covered. >> >> I do think though that it would be a good idea to put a line in the book saying that you *either* use the wpa_supplicant.service with dbus (if you're thinking of installing Network Manager later) *or* [email protected]. I had a lot of initial trouble getting on line because I enabled both of them and they interfered with each other. > > Thank you very much for testing on your system. Interesting that you're not seeing the same behaviour as I am (lfs-systemd 7.7 + blfs being a mix of 7.6-systemd and 7.7-sysv). > > If you run "/sbin/wpa_supplicant --help", are there multiple entries in the "driver" section of the output? I get: > > drivers: > nl80211 = Linux nl80211/cfg80211 > wext = Linux wireless extensions (generic) > wired = Wired Ethernet driver > > And when running wpa_supplicant directly (with all other relevant processes stopped), here is what happens: > > # trying without "-D" > wpa_supplicant -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant-wlp3s0.conf > > Sep 03 13:40:23 t550-lfs kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled > Sep 03 13:40:23 t550-lfs kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled > Sep 03 13:40:23 t550-lfs kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready > (then no more output) > > # trying with "-D" > wpa_supplicant -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant-wlp3s0.conf -Dwext > > Sep 03 13:41:07 t550-lfs kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled > Sep 03 13:41:07 t550-lfs kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled > Sep 03 13:41:07 t550-lfs kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready > Sep 03 13:41:07 t550-lfs kernel: cfg80211: Calling CRDA for country: AT > Sep 03 13:41:08 t550-lfs kernel: cfg80211: Calling CRDA for country: AT > Sep 03 13:41:11 t550-lfs kernel: wlp3s0: authenticate with a0:f3:c1:f8:8e:c9 > Sep 03 13:41:11 t550-lfs kernel: wlp3s0: send auth to a0:f3:c1:f8:8e:c9 (try 1/3) > Sep 03 13:41:11 t550-lfs kernel: wlp3s0: authenticated > Sep 03 13:41:11 t550-lfs kernel: wlp3s0: associate with a0:f3:c1:f8:8e:c9 (try 1/3) > Sep 03 13:41:11 t550-lfs kernel: wlp3s0: RX AssocResp from a0:f3:c1:f8:8e:c9 (capab=0x431 status=0 aid=1) > Sep 03 13:41:11 t550-lfs kernel: wlp3s0: associated > Sep 03 13:41:11 t550-lfs kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready > > Regards, > Simon
Hi Simon, I may be wrong on this (I am responding on my phone as I am away from my PC), but if I remember correctly, the backend that you use depends upon the driver that your card uses. Some need the backend specified and some don't. I have never personally had a card that requires this, but I know that such cards exist. Douglas R. Reno
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
