Re: wifi connection tool?
On 2014-12-29 01:07:48 +0100, Vincent Lefevre wrote:
> 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.
[...]
This was when the GUI was running.
I had also done a check a few days ago when the GUI was not running,
and also got a disconnection, and thought that there was the same
problem. Actually I think that I didn't wait for long enough. Indeed,
a few minutes ago, with wpa_cli running, I could see messages in
real time (which helps a lot since this shows some activity despite
temporary failures):
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz)
<3>Association request to the driver failed
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1
<3>CTRL-EVENT-TERMINATING
Connection to wpa_supplicant lost - trying to reconnect
Connection to wpa_supplicant re-established
<3>Authentication with 00:1f:33:89:73:4e timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz)
<3>Association request to the driver failed
<3>Authentication with 00:1f:33:89:73:4e timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="lefevre" auth_failures=1 duration=10 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="lefevre"
<3>Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz)
<3>Association request to the driver failed
<3>Associated with 00:1f:33:89:73:4e
<3>WPA: Key negotiation completed with 00:1f:33:89:73:4e [PTK=CCMP GTK=CCMP]
<3>CTRL-EVENT-CONNECTED - Connection to 00:1f:33:89:73:4e completed [id=0 id_str=]
In /var/log/wicd/wicd.log, I now have:
[...]
2014/12/29 01:25:32 :: ifconfig wlan0 0.0.0.0
2014/12/29 01:25:32 :: /sbin/ip route flush dev wlan0
2014/12/29 01:25:32 :: ifconfig wlan0 down
2014/12/29 01:25:32 :: ifconfig wlan0 up
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/avahi-daemon with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/bridge with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/wireless-tools with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/wireless-tools returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/wpasupplicant with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2014/12/29 01:25:32 :: wpa_cli -i wlan0 terminate
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/avahi-autoipd with params
2014/12/29 01:25:32 :: /etc/network/if-down.d/avahi-autoipd returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/bind9 with params
2014/12/29 01:25:32 :: /etc/network/if-down.d/bind9 returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/postfix with params
2014/12/29 01:25:32 :: /etc/network/if-down.d/postfix returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/resolvconf with params
2014/12/29 01:25:32 :: /etc/network/if-down.d/resolvconf returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/upstart with params
2014/12/29 01:25:32 :: /etc/network/if-down.d/upstart returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-down.d/wpasupplicant with params
2014/12/29 01:25:32 :: /etc/network/if-down.d/wpasupplicant returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/avahi-daemon with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/bridge with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/bridge returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/wireless-tools with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/wireless-tools returned 0
2014/12/29 01:25:32 :: Executing /etc/network/if-post-down.d/wpasupplicant with params
2014/12/29 01:25:32 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2014/12/29 01:25:35 :: ifconfig wlan0
2014/12/29 01:25:35 :: Autoconnecting...
2014/12/29 01:25:35 :: Starting wireless autoconnect...
[...]
So, all that I need to do is to make sure that the GUI is not open
and wait for several dozens of seconds. Otherwise...
Concerning the problem with the GUI, this is the bug I had already
reported 4 years ago:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582567
except that, though I still use debug mode, I no longer get the
Skipping autoconnect because GUI is open
log message I had before!
I'll try the patch by Tom Van Braeckel. If I understand correctly,
it has been merged upstream on 2014-12-11, and there will be a new
upstream release (1.7.3) soon.
--
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: