Re: wifi connection tool?
On 2014-12-28 12:43:19 -0800, Don Armstrong wrote:
> On Sun, 28 Dec 2014, Vincent Lefevre wrote:
> > Is there a wifi connection tool that can reconnect *automatically*
> > after a disconnection? (This can happen several times per hour, though
> > the wifi quality is not very bad.)
> >
> > I'm currently using wicd, but it doesn't reconnect automatically.
>
> wpa_supplicant should reconnect automatically, which is what wicd uses.
> If not, run wpa_cli and see what the debugging output is.
When wpa_cli is running and a disconnection occurs, I get:
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0
<3>CTRL-EVENT-TERMINATING
Connection to wpa_supplicant lost - trying to reconnect
and wpa_supplicant is no longer running.
According to /var/log/syslog, the disconnection starts with the
following messages:
Dec 28 22:41:19 xvii kernel: [21420.418746] wlan0: deauthenticated from 00:1f:33:89:73:4e (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Dec 28 22:41:19 xvii kernel: [21420.444406] cfg80211: Calling CRDA to update world regulatory domain
Dec 28 22:41:19 xvii kernel: [21420.831396] cfg80211: Calling CRDA to update world regulatory domain
In /var/log/wicd/wicd.log I have:
[...]
2014/12/28 22:41:17 :: ifconfig wlan0
2014/12/28 22:41:17 :: iwconfig wlan0
2014/12/28 22:41:19 :: ifconfig wlan0
2014/12/28 22:41:19 :: iwconfig wlan0
2014/12/28 22:41:21 :: ifconfig wlan0
2014/12/28 22:41:21 :: iwconfig wlan0
2014/12/28 22:41:21 :: Forced disconnect on
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/avahi-autoipd with params
2014/12/28 22:41:21 :: /etc/network/if-down.d/avahi-autoipd returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/bind9 with params
2014/12/28 22:41:21 :: /etc/network/if-down.d/bind9 returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/postfix with params
2014/12/28 22:41:21 :: /etc/network/if-down.d/postfix returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/resolvconf with params
2014/12/28 22:41:21 :: /etc/network/if-down.d/resolvconf returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/upstart with params
2014/12/28 22:41:21 :: /etc/network/if-down.d/upstart returned 0
2014/12/28 22:41:21 :: Executing /etc/network/if-down.d/wpasupplicant with params
2014/12/28 22:41:21 :: /etc/network/if-down.d/wpasupplicant returned 0
2014/12/28 22:41:21 :: attempting to set hostname with dhclient
2014/12/28 22:41:21 :: using dhcpcd or another supported client may work better
2014/12/28 22:41:21 :: /sbin/dhclient -v -r wlan0
[...]
2014/12/28 22:41:22 :: ifconfig wlan0 0.0.0.0
2014/12/28 22:41:22 :: /sbin/ip route flush dev wlan0
2014/12/28 22:41:22 :: ifconfig wlan0 down
2014/12/28 22:41:22 :: ifconfig wlan0 up
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/avahi-daemon with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/bridge with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wireless-tools with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wireless-tools returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wpasupplicant with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2014/12/28 22:41:22 :: wpa_cli -i wlan0 terminate
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/avahi-autoipd with params
2014/12/28 22:41:22 :: /etc/network/if-down.d/avahi-autoipd returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/bind9 with params
2014/12/28 22:41:22 :: /etc/network/if-down.d/bind9 returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/postfix with params
2014/12/28 22:41:22 :: /etc/network/if-down.d/postfix returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/resolvconf with params
2014/12/28 22:41:22 :: /etc/network/if-down.d/resolvconf returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/upstart with params
2014/12/28 22:41:22 :: /etc/network/if-down.d/upstart returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-down.d/wpasupplicant with params
2014/12/28 22:41:22 :: /etc/network/if-down.d/wpasupplicant returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/avahi-daemon with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/bridge with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wireless-tools with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wireless-tools returned 0
2014/12/28 22:41:22 :: Executing /etc/network/if-post-down.d/wpasupplicant with params
2014/12/28 22:41:22 :: /etc/network/if-post-down.d/wpasupplicant returned 0
[...]
If I understand correctly, wicd notices the disconnection and chooses
to terminate wpa_supplicant.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: