Re: wifi connection tool?
On Lu, 29 dec 14, 15:58:06, Vincent Lefevre wrote: This is for Network Manager (which I'm not using since it handles the full network configuration, but I already have my own for Ethernet, and I don't want it to be broken). If I'm not mistaken it can be configured to not handle connections already handled by ifupdown. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: wifi connection tool?
Andrei POPESCU andreimpope...@gmail.com writes: On Lu, 29 dec 14, 15:58:06, Vincent Lefevre wrote: This is for Network Manager (which I'm not using since it handles the full network configuration, but I already have my own for Ethernet, and I don't want it to be broken). If I'm not mistaken it can be configured to not handle connections already handled by ifupdown. Network devices which are configured in /etc/network/interfaces will typically be managed by ifupdown. Such devices will by default be marked as unmanaged in NetworkManager. From /usr/share/doc/network-manager/README.Debian I used to run a configuration like that, so I can confirm that this works indeed. (For completeness' sake: I used to have the static network config of my workstation configured on the box itself, until I decided that it would be a lot simpler to just set up a static association on my DHCP server and just let NM handle all the network issues on my clients) Mart -- We will need a longer wall when the revolution comes. --- AJS, quoting an uncertain source. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8661ctjh08@gaheris.avalon.lan
Re: wifi connection tool?
On 12/30/2014 07:26 AM, Mart van de Wege wrote: Andrei POPESCU andreimpope...@gmail.com writes: On Lu, 29 dec 14, 15:58:06, Vincent Lefevre wrote: This is for Network Manager (which I'm not using since it handles the full network configuration, but I already have my own for Ethernet, and I don't want it to be broken). If I'm not mistaken it can be configured to not handle connections already handled by ifupdown. Network devices which are configured in /etc/network/interfaces will typically be managed by ifupdown. Such devices will by default be marked as unmanaged in NetworkManager. From /usr/share/doc/network-manager/README.Debian I used to run a configuration like that, so I can confirm that this works indeed. (For completeness' sake: I used to have the static network config of my workstation configured on the box itself, until I decided that it would be a lot simpler to just set up a static association on my DHCP server and just let NM handle all the network issues on my clients) Mart In addition, if you'd like to manually tell n-m to not manage interfaces, you can add a section like this to your /etc/NetworkManager/NetworkManager.conf: [keyfile] unmanaged-devices=mac:01:02:03:04:05:06;mac:00:11:22:33:44:55 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54a2f7fe.4010...@mattventura.net
Re: wifi connection tool?
Did you read this article? http://www.linuxx.eu/2014/03/automatically-reconnect-wifi-debian.html There is another blog, you might find interesting: http://www.linuxquestions.org/questions/linux-wireless-networking-41/reconnect-to-wireless-network-386754/ And last but not least, maybe this blog might bve also usefull: http://ubuntuforums.org/showthread.php?p=8580879 Good luck! Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1783060.IVexgZxuj4@protheus2
Re: wifi connection tool?
On 2014-12-29 12:04:24 +0100, Hans wrote: Did you read this article? http://www.linuxx.eu/2014/03/automatically-reconnect-wifi-debian.html This is for Network Manager (which I'm not using since it handles the full network configuration, but I already have my own for Ethernet, and I don't want it to be broken). There is another blog, you might find interesting: http://www.linuxquestions.org/questions/linux-wireless-networking-41/reconnect-to-wireless-network-386754/ It seems to be for a machine that uses wifi only. And last but not least, maybe this blog might bve also usefull: http://ubuntuforums.org/showthread.php?p=8580879 It suggests either Network Manager (not OK) or wicd (buggy). Now, concerning wicd, I've written a patch last night (the upstream one doesn't solve the problem), and I'm still waiting for the next disconnection to see if it works... -- Vincent Lefèvre vinc...@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) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141229145806.ge20...@xvii.vinc17.org
wifi connection tool?
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. The tool must handle wifi *only*, not Ethernet (which I use at some places and for which I have my own, specific set-up). -- Vincent Lefèvre vinc...@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) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141228202620.ga20...@xvii.vinc17.org
Re: wifi connection tool?
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. -- Don Armstrong http://www.donarmstrong.com Nearly all men can stand adversity, but if you really want to test his character, give him power. -- Abraham Lincoln -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141228204319.gz12...@teltox.donarmstrong.com
Re: wifi connection tool?
Am Sonntag, 28. Dezember 2014, 21:26:20 schrieb Vincent Lefevre: 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. Did you set automatically connection in the gui? Here it is working, when I activate this. However, I did not test it with the demon or the ncurses option. Best Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3013225.5AvPbNJm1y@protheus2
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: 3CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0 3CTRL-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.06] 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
Re: wifi connection tool?
On 2014-12-28 22:13:30 +0100, Hans wrote: Am Sonntag, 28. Dezember 2014, 21:26:20 schrieb Vincent Lefevre: 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. Did you set automatically connection in the gui? Yes. Here it is working, when I activate this. Here it seems to work, i.e. when I boot the machine, wicd automatically connects to this network. But in the case of a disconnection from the kernel, it seems that wicd interprets this as a disconnection by the user, so that it terminates wpa_supplicant and does not try to reconnect. However, I did not test it with the demon or the ncurses option. This option is available in the GUI, but AFAIK, it is for the daemon. -- Vincent Lefèvre vinc...@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) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141229001321.gc20...@xvii.vinc17.org
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: 3CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0 3CTRL-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): 3CTRL-EVENT-SCAN-RESULTS 3CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=0 3CTRL-EVENT-SCAN-RESULTS 3WPS-AP-AVAILABLE 3Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz) 3Association request to the driver failed 3CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1 3CTRL-EVENT-TERMINATING Connection to wpa_supplicant lost - trying to reconnect Connection to wpa_supplicant re-established 3Authentication with 00:1f:33:89:73:4e timed out. 3CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1 3CTRL-EVENT-SCAN-RESULTS 3WPS-AP-AVAILABLE 3Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz) 3Association request to the driver failed 3Authentication with 00:1f:33:89:73:4e timed out. 3CTRL-EVENT-DISCONNECTED bssid=00:1f:33:89:73:4e reason=3 locally_generated=1 3CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid=lefevre auth_failures=1 duration=10 reason=CONN_FAILED 3CTRL-EVENT-SCAN-RESULTS 3WPS-AP-AVAILABLE 3CTRL-EVENT-SCAN-RESULTS 3WPS-AP-AVAILABLE 3CTRL-EVENT-SCAN-RESULTS 3WPS-AP-AVAILABLE 3CTRL-EVENT-SSID-REENABLED id=0 ssid=lefevre 3Trying to associate with 00:1f:33:89:73:4e (SSID='lefevre' freq=2472 MHz) 3Association request to the driver failed 3Associated with 00:1f:33:89:73:4e 3WPA: Key negotiation completed with 00:1f:33:89:73:4e [PTK=CCMP GTK=CCMP] 3CTRL-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
