On Thu, Mar 26, 2015 at 08:02:37PM -0700, Adrian Chadd wrote: > Ooooooooh. I think you're hitting the "multiple wpa_supplicant > processes are running at startup" bug. :( > ...
During a bit of exploring this morning, I'm not seeing evidence that I recognize as corroborating that suggestion. For one thing, the messages logged by wpa_supplicant (in /var/log/messages) report just the one PID (until I manually wade in and start breaking things). For another, there is a /var/run/wpa_supplicant/wlan0.pid created & populated with the PID. (And yes, its contents match the PID logged in the above-cited messages.) During my experiments, I found some "interesting" behavior: * I set up the em0 & iwn0/wlan0 interfaces as described in the "laptop" example (31.3) at <https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html> (subsitituting "em0" for "bge0"): g1-254(10.1-S)[5] egrep 'ifconfig|(em|lagg|wlan)0' rc.conf | grep -v '^#' ifconfig_em0="up" ifconfig_iwn0="ether 00:24:e8:b5:85:46" wlans_iwn0=wlan0 ifconfig_wlan0="WPA" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP" g1-254(10.1-S)[6] * Immediately subsequent to the transition from single- to multi-user mode: + em0 is active + WiFi LED is blinking rapidly (indicating failed attempts at association) + wlan0 shows "no carrier" + lagg0 shows "active", but the inet address is (still) 0.0.0.0. * If I: + "pgrep wpa_supplicant", only a single PID is returned. + "pkill wpa_supplicant", the WiFi LED goes out; if I then follow that with another "pgrep wpa_supplicant", no PID is returned. + Out of perversity, I then verified that "ifconfig wlan0" reported the status of wlan0 (implying tha wlan0 exists). + "service netif stop wlan0 iwn0", I get a whimper: wpa_supplicant not running? (check /var/run/wpa_supplicant/wlan0.pid). Stopping Network: wlan0 iwn0. ifconfig: interface wlan0 does not exist + An attempt to "ifconfig wlan0"confirms that it no longer exists. + "ifconfig" shows that em0 is still active, as is lagg0. lagg0 also still has no IP address assigned -- and it no longer has wlan0 as a component. + "service netif start iwn0" yields: Starting wpa_supplicant. Starting Network: iwn0. and wlan0 now exists -- and gets association. But wlan0 has not become part of lagg0 as a result of this. + "service netif restart lagg0" yields: Stopping dhclient. Waiting for PIDS: 1035. Stopping Network: lagg0. lagg0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 34:e6:d7:3c:4a:93 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect status: active groups: lagg laggproto failover lagghash l2,l3,l4 laggport: em0 flags=5<MASTER,ACTIVE> Destroyed clone interfaces: lagg0. Created clone interfaces: lagg0. Starting dhclient. dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT dhclient: Leaving hostname set to and the WiFi LED went from solid "on" to "blinking madly" -- and the system then locks up hard -- requiring a power-cycle to do anything. (The BIOS has an option for an "unobtrusive mode" -- if this is enabled (which I did), Fn+B will blank the screen and make all lights on the device go out. I had tried this earlier, and it seems to work as advertised; the Fn+B is a toggle. When the above-described "lock up" occurred, I tried "Fn+B".... no reaction at all. Yeah, I tried a few other things -- even switching the WiFi switch to "off" didn't stop the WiFi LED from blinking madly.) (I have a typescript showing that stuff....) Peace, david -- David H. Wolfskill da...@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
pgp75jklPzM3N.pgp
Description: PGP signature
