does not notice if authentication failed on open network

Bug #723194 reported by Josh Watzman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
New
Undecided
Unassigned

Bug Description

wicd version 1.7.0 on my Debian sid system fails to notice if authentication fails. My campus uses an open wireless network, but access points will sometimes deny a connection request if they are overloaded, hoping that the connecting machine will fail over to a less-loaded access point. wicd not only does not do this, but it doesn't notice that the system is not connected to the access point and tries in vain to get an IP address instead of failing and/or trying again and/or trying another access point with the same SSID.

Here's an example dmesg and wicd.log snipped from an autoconnect to this network on boot until when I cancelled the connection. Note that the machine at no time during these logs was actually associated with the network.

dmesg
[ 30.045645] sky2 0000:02:00.0: eth0: enabling interface
[ 30.049052] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 35.601521] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 36.288056] sky2 0000:02:00.0: eth0: disabling interface
[ 36.294781] sky2 0000:02:00.0: eth0: enabling interface
[ 36.296651] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 36.677771] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 38.716674] wlan0: direct probe to 00:1a:1e:91:21:a0 (try 1)
[ 38.717184] wlan0: direct probe to 00:1a:1e:91:21:a0 (try 1)
[ 38.917112] wlan0: authenticate with 00:1a:1e:88:1b:20 (try 1)
[ 38.921752] wlan0: 00:1a:1e:88:1b:20 denied authentication (status 17)

/var/log/wicd/wicd.log
2011/02/22 10:24:54 :: ---------------------------
2011/02/22 10:24:54 :: wicd initializing...
2011/02/22 10:24:54 :: ---------------------------
2011/02/22 10:24:54 :: wicd is version 1.7.0 552
2011/02/22 10:24:54 :: setting backend to external
2011/02/22 10:24:54 :: trying to load backend external
2011/02/22 10:24:54 :: successfully loaded backend external
2011/02/22 10:24:54 :: trying to load backend external
2011/02/22 10:24:54 :: successfully loaded backend external
2011/02/22 10:24:54 :: Automatically detected wireless interface wlan0
2011/02/22 10:24:54 :: setting wireless interface wlan0
2011/02/22 10:24:54 :: automatically detected wired interface eth0
2011/02/22 10:24:54 :: setting wired interface eth0
2011/02/22 10:24:54 :: setting wpa driver wext
2011/02/22 10:24:54 :: setting use global dns to False
2011/02/22 10:24:54 :: setting global dns
2011/02/22 10:24:54 :: global dns servers are None None None
2011/02/22 10:24:54 :: domain is None
2011/02/22 10:24:54 :: search domain is None
2011/02/22 10:24:54 :: setting automatically reconnect when connection drops True
2011/02/22 10:24:54 :: Setting dhcp client to 1
2011/02/22 10:24:54 :: Wireless configuration file found...
2011/02/22 10:24:54 :: Wired configuration file found...
2011/02/22 10:24:54 :: chmoding configuration files 0600...
2011/02/22 10:24:54 :: chowning configuration files root:root...
2011/02/22 10:24:54 :: Using wireless interface...wlan0
2011/02/22 10:24:54 :: Using wired interface...eth0
2011/02/22 10:25:02 :: Autoconnecting...
2011/02/22 10:25:02 :: No wired connection present, attempting to autoconnect to wi
reless network
2011/02/22 10:25:04 :: trying to automatically connect to...CMU
2011/02/22 10:25:04 :: Connecting to wireless network CMU
2011/02/22 10:25:04 :: attempting to set hostname with dhclient
2011/02/22 10:25:04 :: using dhcpcd or another supported client may work better
2011/02/22 10:25:06 :: attempting to set hostname with dhclient
2011/02/22 10:25:06 :: using dhcpcd or another supported client may work better
2011/02/22 10:25:06 :: Putting interface down
2011/02/22 10:25:06 :: Releasing DHCP leases...
2011/02/22 10:25:06 :: attempting to set hostname with dhclient
2011/02/22 10:25:06 :: using dhcpcd or another supported client may work better
2011/02/22 10:25:06 :: Setting false IP...
2011/02/22 10:25:06 :: Stopping wpa_supplicant
2011/02/22 10:25:06 :: Flushing the routing table...
2011/02/22 10:25:06 :: Putting interface up...
2011/02/22 10:25:08 :: Running DHCP with hostname queenoflight
2011/02/22 10:25:08 :: attempting to set hostname with dhclient
2011/02/22 10:25:08 :: using dhcpcd or another supported client may work better
2011/02/22 10:25:08 :: Internet Systems Consortium DHCP Client 4.1.1-P1
2011/02/22 10:25:08 :: Copyright 2004-2010 Internet Systems Consortium.
2011/02/22 10:25:08 :: All rights reserved.
2011/02/22 10:25:08 :: For info, please visit https://www.isc.org/software/dhcp/
2011/02/22 10:25:08 ::
2011/02/22 10:25:08 :: Listening on LPF/wlan0/00:17:f2:e6:9a:f0
2011/02/22 10:25:08 :: Sending on LPF/wlan0/00:17:f2:e6:9a:f0
2011/02/22 10:25:08 :: Sending on Socket/fallback
2011/02/22 10:25:12 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
2011/02/22 10:25:18 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
2011/02/22 10:25:26 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
2011/02/22 10:25:33 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
2011/02/22 10:25:42 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
2011/02/22 10:25:50 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
2011/02/22 10:25:53 :: canceling connection attempt

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.