Apologies for the very long delay in responding to this bug from back in May. I ended up turning off wicd because I ran out of time to work on debugging the problem and just needed to use the network, and then didn't get back to this.
David Paleino <[email protected]> writes: > Let's try something. >> wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/001310d30b2a -D >> wext iwconfig wlan0 essid -- Eyrie >> iwconfig wlan0 channel 3 >> iwconfig wlan0 ap 00:13:10:D3:0B:2A >> /sbin/dhclient -cf /var/lib/wicd/dhclient.conf wlan0 > What happens if you add -lf /var/lib/dhcp3/dhclient.wlan0.leases to the last > command? Does it get a lease? This I didn't try, however: > OTOH, if you move dhclient.wlan0.leases out of the way, or empty it, > does "ifup wlan0" still work? Yes, this still worked. But whatever the problem is seems to be specific to 64-bit WEP. I replaced my wireless router recently with a new one, and I've also tried using wicd while travelling, and everything now works fine with either 128-bit WEP or WPA. I'm not sure what to make of that; I suppose it still could be some sort of wicd problem, but that makes me suspect the wireless kernel driver instead, or some other weird interaction. At this point, I can no longer reproduce the problem with any of the wireless networks that I still use. I was only having it with that one wireless router. So I suspect that, unless other people have also seen the problem, this bug can just be closed. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
