POMdev wrote: > Checking the 7 radios here, wpa_cli was not running on 4 of them! So, > for these radios at that time, a simple re-association would not be > enough to keep SqueezePlay or jive happy. > > The latest 0.7.5 code on the GitHub development branch includes a > function to check if wpa_cli is running, and, if not, to relaunch it. > This is called before every ping test. Preliminary testing here shows > that the wpa_cli is being relaunched at more or less random times > unrelated to wireless connectivity, including on radios that have had no > serious ping failures or restarts. > > Either wpa_cli is exiting on its own, or something else (I hope not the > script) is killing it. Of course, the hard reset kills and relaunches > it, but that has always worked. I doubt it is the script. I will read > through the wpa_cli code and see about adding or enabling debug logging > to pinpoint this phenomenon. BTW, the recEvent utility also casts > suspicion on wpa_supplicant or wpa_client, see the earlier post on this.
I think it be very helpful to find out what is killing it. If it is not the script, then that may hint at a problem with -wpa_supplicant-, or with its control socket. Some additional notes. There is room for error ! The reason, I think, that -wpa_cli- is being run as a daemon is to react to events from -wpa_supplicant-. The only thing it is actually doing is to "kick" -udhcpc- into renewing the lease when a connection event is noted. As far I can tell, that is all it is doing. SqueezePlay itself does not require -wpa_cli- be running, other than to deliver that kick, because it communicates with -wpa_supplicant- directly through its control socket (as does -wpa_cli-). The socket is -/var/run/wpa_supplicant/eth1-. SqueezePlay does restart -wpa_cli- when it brings a network up. (-Networking.lua- function -_ifiup- calls -restartWpaCli-). SqueezePlay itself does have the ability to respond to events from -wpa_supplicant- if it chooses. But it does not so choose. See -attach- / -detach- following -jive.net.Networking:request()-. That might be a route towards logging -wpa_supplicant- events. -wpa_cli- will work from the command line regardless of whether it is running as a daemon. But it is the daemonized instance that would "kick" -udhcpc- when a reconnection takes place. ------------------------------------------------------------------------ mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
