David Paleino <[email protected]> writes:

> What happens if you manually run these commands, in this exact order?

> 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

This fails the same way wicd does:

wanderer:/root# wpa_supplicant -B -i wlan0 -c 
/var/lib/wicd/configurations/001310d30b2a -D wext
wanderer:/root# iwconfig wlan0 essid -- Eyrie
wanderer:/root# iwconfig wlan0 channel 3
wanderer:/root# iwconfig wlan0 ap 00:13:10:D3:0B:2A
wanderer:/root# /sbin/dhclient -cf /var/lib/wicd/dhclient.conf wlan0
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/00:19:7e:6c:60:92
Sending on   LPF/wlan0/00:19:7e:6c:60:92
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

iwconfig was showing a valid association with the AP while DHCP was
failing.

> From the log, it really seems dhclient failing to get a lease, not
> wicd's fault:

> 2010/05/30 13:46:19 :: Listening on LPF/wlan0/00:19:7e:6c:60:92
> 2010/05/30 13:46:19 :: Sending on   LPF/wlan0/00:19:7e:6c:60:92
> 2010/05/30 13:46:19 :: Sending on   Socket/fallback
> 2010/05/30 13:46:23 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67
> interval 4
> [..]
> 2010/05/30 13:47:24 :: No DHCPOFFERS received.
> 2010/05/30 13:47:24 :: No working leases in persistent database - sleeping.
> 2010/05/30 13:47:24 :: DHCP connection failed

> And wicd correctly parses this as "dhcp_failed"

For some reason, the way that wicd is calling dhclient is not working,
whereas the way that ifup is calling it is working fine.  Strange.

> Can you run "ifup --verbose wlan0", and attach it here? (I hope that
> gives us enough information).

Here you go:

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf 
/var/lib/dhcp3/dhclient.wlan0.leases wlan0
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/00:19:7e:6c:60:92
Sending on   LPF/wlan0/00:19:7e:6c:60:92
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 172.18.0.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 172.18.0.1
bound to 68.65.160.233 -- renewal in 1184 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

-- 
Russ Allbery ([email protected])               <http://www.eyrie.org/~eagle/>



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to