On Sun, 30 May 2010 14:14:50 -0700, Russ Allbery wrote:

> David Paleino <da...@debian.org> writes:
> > Also, if the above doesn't work, would you please post
> > /var/log/wicd/wicd.log , after enabling debugging mode?
> 
> Here are the versions of the relevant software:
> 
> ii  dhcp3-client                         3.1.3-2
> ii  ifupdown                             0.6.10
> ii  wicd                                 1.7.0+ds1-5
> ii  wicd-daemon                          1.7.0+ds1-5
> 
> I also tried installing dhcpcd 1:3.2.3-5, but there was no change in
> behavior.  My /etc/network/interfaces file is very simple:
> 
> === start ===
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> === end ===

This should be fine.

> iwconfig shows that the wireless network is up and associated with the
> base station, and /var/log/syslog confirms.  But I'm unable to get a DHCP
> lease when the session is initiated by wicd on my home network.  I'm
> intermittantly able to get a DHCP lease on other networks via wicd, but it
> often requires stopping the connection, unloading the wireless driver
> (ath9k), reloading it, stopping and restarting wicd, and attempting a
> connection again, or similar sorts of fiddling.

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

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"

(btw, I also see a traceback in the log, but that should be harmless, or at
least not much relevant to this bug)

I also see that dhcpcd itself fails:

2010/05/30 13:55:52 :: /sbin/dhcpcd -h wanderer --noipv4ll wlan0 
[..]
2010/05/30 13:56:12 :: err, wlan0: timed out

(in the log, all the "iwconfig wlan0" lines are wicd trying to determine
the network status)

> Attached are the results of the insserv test suite and the wicd.log.  The
> wicd.log shows multiple attempts, including some with dhcpcd instead of
> dhclient.  I've replaced instances of my passphrase with <passphrase>.
> Note that this is a fairly old base station that only does WEP.
> 
> If I stop wicd and then manually add the wireless configuration into
> /etc/network/interfaces like:
> 
> === start ===
> allow-hotplug wlan0
> auto wlan0
> iface wlan0 inet dhcp
>         dns-nameservers 171.64.7.121 171.64.7.77 171.64.7.99 171.64.7.55
>         dns-search stanford.edu
>         wireless-essid Eyrie
>         wireless-ap 00:13:10:d3:0b:2a
>         wireless-key <key> restricted
>         wireless-channel 3
> === end ===
> 
> and then run ifup wlan0, everything works great and I get a DHCP lease
> immediately.

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

> Note that while this configuration forces the AP, running iwconfig while wicd
> was trying showed an association, so I don't think missing configuration
> there is what's going on.

Well, wicd succeeds at associating, it (wicd itself, or DHCP clients) just
doesn't get an IP <g> :)

Thanks for your time and help,
David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: PGP signature

Reply via email to