Wicd tries to obtain IP address before associating with the AP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wicd |
New
|
Undecided
|
Unassigned |
Bug Description
This seems to happen only with open networks (no encryption), when trying to connect to an open network it often fails to obtain IP address. When investigating, I found that while wicd was reporting "Obtaining IP address...", iwconfig would report "Access Point: Not-Associated".
I'm guessing wicd should verify the association before trying to obtain IP address.
To make it work, I use this bash function , which I run while wicd is in the "Obtaining IP address..." status, and makes it connect successfully.
wifi_assoc(){
for i in `seq 1 5`
do
IW=`sudo iwconfig`
echo "$IW" | grep 'Not-Assoc' && {
echo "Trying to assiciate with $NET"
sudo iw dev wlan0 connect -w "$NET"
}
sleep 1
done
}
I'm guessing this doesn't happen to everyone since it would have been reported, so maybe there is some kind of incompatibility with my network card. When I try to associate, it will often fail with a "invalid argument (-22)" error, that's why in the function it tries to associate several times.
I'm using wicd 1.7.2.4 (bzr-r30) in ubuntu 14.04, my wifi card is a Centrino Advanced-N 6235
I think I am experiencing the same bug. My spec is:
Slackware 14.2 64bits
Wicd 1.7.4
Broadcom BCM43228 wifi chip
This happens for me on the majority of open/no encryption wifi networks. And I've experienced this over a number of years, over several versions of Slackware and wicd. For the first time yesterday I discovered that the only way to overcome this is to set a dummy fixed IP in wicd, and after it connects to run dhcpcd on the command line.
It would be really great if someone would take a closer look at this bug.