Arch Linux

Rhino

Member

Registered: 2007-12-17

Posts: 7

Website

DHCP problem

I'm using wicd with iwlwifi 3945 on my laptop but I can't get DHCP to work. I can connect to my network using a static address but whenever I try using DHCP, wicd stucks at : Obtaining ip address...

Dec 17 15:58:01 Aurora dhclient: Internet Systems Consortium DHCP Client V3.0.6
Dec 17 15:58:01 Aurora dhclient: Copyright 2004-2007 Internet Systems Consortium.
Dec 17 15:58:01 Aurora dhclient: All rights reserved.
Dec 17 15:58:01 Aurora dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Dec 17 15:58:01 Aurora dhclient:
Dec 17 15:58:01 Aurora ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 17 15:58:01 Aurora dhclient: wmaster0: unknown hardware address type 801
Dec 17 15:58:02 Aurora dhclient: wmaster0: unknown hardware address type 801
Dec 17 15:58:02 Aurora dhclient: Listening on LPF/wlan0/00:13:02:b2:14:cc
Dec 17 15:58:02 Aurora dhclient: Sending on   LPF/wlan0/00:13:02:b2:14:cc
Dec 17 15:58:02 Aurora dhclient: Sending on   Socket/fallback
Dec 17 15:58:05 Aurora dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 17 15:58:05 Aurora dhclient: DHCPNAK from 192.168.100.1
Dec 17 15:58:05 Aurora ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 17 15:58:06 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Dec 17 15:58:06 Aurora dhclient: receive_packet failed on wlan0: Network is down
Dec 17 15:58:09 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Dec 17 15:58:15 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Dec 17 15:58:24 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Dec 17 15:58:37 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Dec 17 15:58:52 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Dec 17 15:59:03 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Dec 17 15:59:07 Aurora dhclient: No DHCPOFFERS received.
Dec 17 15:59:07 Aurora dhclient: No working leases in persistent database - sleeping.
Dec 17 16:00:19 Aurora dhclient: receive_packet failed on wlan0: Network is down
Dec 17 16:00:19 Aurora ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 17 16:00:20 Aurora wlan0: Initial auth_alg=0
Dec 17 16:00:20 Aurora wlan0: authenticate with AP 00:13:46:bb:3a:b2
Dec 17 16:00:20 Aurora wlan0: RX authentication from 00:13:46:bb:3a:b2 (alg=0 transaction=2 status=0)
Dec 17 16:00:20 Aurora wlan0: authenticated
Dec 17 16:00:20 Aurora wlan0: associate with AP 00:13:46:bb:3a:b2
Dec 17 16:00:20 Aurora wlan0: RX ReassocResp from 00:13:46:bb:3a:b2 (capab=0x21 status=0 aid=2)
Dec 17 16:00:20 Aurora wlan0: associated
Dec 17 16:00:20 Aurora wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
Dec 17 16:00:20 Aurora wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
Dec 17 16:00:20 Aurora wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
Dec 17 16:00:20 Aurora wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
Dec 17 16:00:20 Aurora ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 17 16:00:20 Aurora dhclient: There is already a pid file /var/run/dhclient.pid with pid 27656
Dec 17 16:00:20 Aurora dhclient: removed stale PID file
Dec 17 16:00:20 Aurora dhclient: Internet Systems Consortium DHCP Client V3.0.6
Dec 17 16:00:20 Aurora dhclient: Copyright 2004-2007 Internet Systems Consortium.
Dec 17 16:00:20 Aurora dhclient: All rights reserved.
Dec 17 16:00:20 Aurora dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Dec 17 16:00:20 Aurora dhclient:
Dec 17 16:00:20 Aurora dhclient: wmaster0: unknown hardware address type 801
Dec 17 16:00:21 Aurora dhclient: wmaster0: unknown hardware address type 801
Dec 17 16:00:21 Aurora dhclient: Listening on LPF/wlan0/00:13:02:b2:14:cc
Dec 17 16:00:21 Aurora dhclient: Sending on   LPF/wlan0/00:13:02:b2:14:cc
Dec 17 16:00:21 Aurora dhclient: Sending on   Socket/fallback
Dec 17 16:00:23 Aurora dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 17 16:00:23 Aurora dhclient: DHCPNAK from 192.168.100.1
Dec 17 16:00:23 Aurora ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 17 16:00:24 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Dec 17 16:00:24 Aurora dhclient: receive_packet failed on wlan0: Network is down
Dec 17 16:00:28 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Dec 17 16:00:36 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Dec 17 16:00:49 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Dec 17 16:00:59 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Dec 17 16:01:15 Aurora dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Dec 17 16:01:25 Aurora dhclient: No DHCPOFFERS received.
Dec 17 16:01:25 Aurora dhclient: No working leases in persistent database - sleeping.

I tried everything and I can't make it works, it's the only thing that keeps me on windows, my school network being unreachable in static. Thanks in advance for your help.

Sorry for my bad english.

fed359

Member

Registered: 2007-11-21

Posts: 46

Re: DHCP problem

Is the network you're trying to connect to encrypted? You'll get a similar result to this if you're using an incorrect key, sometimes wicd likes double quotes around WEP keys.

peart

Member

From: Kanuckistan

Registered: 2003-07-28

Posts: 510

Re: DHCP problem

I just made the switch to iwl3945 from ipw3945.  I had the same problem as you.  I compile my own kernel, without QoS options.  There seems to be a dependency for iwl3945 on QoS, cause without it, the driver works like crap (huge packet loss).

Anyway, now that I have enabled QoS in my kernel, iwl3945 works just as well - if not better - than ipw3945.
Ciao,
peart.

fed359

Member

Registered: 2007-11-21

Posts: 46

Re: DHCP problem

I just made the switch to iwl3945 from ipw3945.  I had the same problem as you.  I compile my own kernel, without QoS options.  There seems to be a dependency for iwl3945 on QoS, cause without it, the driver works like crap (huge packet loss).

Anyway, now that I have enabled QoS in my kernel, iwl3945 works just as well - if not better - than ipw3945.
Ciao,
peart.

Strange, iwl3945 seems to work just fine for me in networkmanager and configuring the interface from terminal with iwconfig. Perhaps this only affects wicd?

Last edited by fed359 (2007-12-17 23:47:43)

Rhino

Member

Registered: 2007-12-17

Posts: 7

Website

Re: DHCP problem

My network is unencrypted.

I have been able to connect in dhcp by connecting in static and then enter in CLI dhcpcd wlan0 but when I closed the connection, I couldn't connect anymore with dhcp.

Also, I used to use networkmanager and dhcp worked so I don't think it's a driver problem. I switch to wicd because I couldn't refresh the network list with networkmanager.

Any other suggestions?

Thanks for your help guys.

fed359

Member

Registered: 2007-11-21

Posts: 46

Re: DHCP problem

It looks like you can change wicd over to use dhcpcd quite easily. Editing /usr/lib/wicd/networking.py and replacing

misc.Run("dhclient " + self.wireless_interface) with misc.Run("dhcpcd " + self.wireless_interface)

and

misc.Run("dhclient " + self.wired_interface) with misc.Run("dhcpcd " + self.wired_interface)

and also

misc.Run("killall dhclient dhclient3 wpa_supplicant") with misc.Run("killall dhcpcd wpa_supplicant")  NOTE: there are 3 of these

you can also change the print lines if you'd like, although that isn't necessary

wicd appeared to work fine with dhcpcd after these changes.

Last edited by fed359 (2007-12-18 01:12:53)

Rhino

Member

Registered: 2007-12-17

Posts: 7

Website

Re: DHCP problem

Guess what? It works!!!

Thanks a lot for your help and the rapidity with which you answered!

(And again, sorry for my bad english.)

fed359

Member

Registered: 2007-11-21

Posts: 46

Re: DHCP problem

Great to hear, just remember that when you update wicd it will change it back to using dhclient, hopefully this won't be a problem in the next version though