On Wed, 2015-03-11 at 20:49 -0400, Stuart D. Gathman wrote: > On Wed, 11 Mar 2015, Dan Williams wrote: > > > On Wed, 2015-03-11 at 15:57 -0500, Alex Ferm wrote: > >> Hello, I'm trying to write a python script that resets NetworkManager > >> when the state is not "NM_STATE_CONNECTED_GLOBAL". Does NetworkManager > >> time out and retry automatically during the "NM_STATE_CONNECTING" state? > >> Also, how is the "NM_STATE_CONNECTED_GLOBAL" determined(ie: is there a > >> periodic ping or something?)? > > > > What's the reason to reset NM when it reports something isn't connected? > > Just to ensure always-on connectivity as hard as possible? Also, what > > do you mean by "reset", what specific actions are you running to do so? > > In my case, wpa_supplicant hangs every so many megabytes, and I have to > killall wpa_supplicant to restore the network connection. I've been > wondering about a way to have NM do that automatically, since fixing > wpa_supplicant seems to be difficult.
You can just "kill -9 wpa_supplicant" from a script somewhere and NM will restart the supplicant automatically via D-Bus activation. Does the hanging supplicant also block D-Bus communication? Can you gdb the supplicant and find out what function it's hung in? Or is it not actually hanging, but just not doing some requested operation? But obviously, fixing wpa_supplicant would be preferable... Dan _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
