dhclient already running, must kill to connect with wireless

Bug #130715 reported by Sheol on 2007-08-06
6
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

Upgraded to gutsy.
I have an Lenovo Thinkpad x61s, with an atheros chipset integrated wireless card.
Since then when I boot my computer up dhclient is already running. In order to connect to the internet I need to bring my card down, kill dhclient
/var/run/dhclient.ath0.pid
bring my car back up
then connect with iwconfig
then manually run dhclient.

Marco Rodrigues (gothicx) wrote :

Hi! If you don't need dhclient, why don't you remove it ?

Sheol (sheol-s) wrote :

Perhaps I wasn't clear. I need dhclient to get a leased an IP address, however there is some program trying to run it all by itself. This is keeping me from connecting to a network I choose.

Sheol (sheol-s) wrote :

Let me be more specific:
I used to connect by:
: iwconfig essid MyNetwork key *****
: dhclient ath0

now it's:
: rm /var/run/dhclient.ath0.pid
: ifdown ath0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7e:a3:99:f7
Sending on LPF/ath0/00:19:7e:a3:99:f7
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.1.1 port 67
Error for wireless request "Set Mode" (8B06) :
    SET failed on device ath0 ; Invalid argument.

: ifconfig ath0 up
: rm /var/run/dhclient.ath0.pid
: iwconfig essid MyNetwork key *****
: dhclient ath0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7e:a3:99:f7
Sending on LPF/ath0/00:19:7e:a3:99:f7
Sending on Socket/fallback
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.110 -- renewal in 17384 seconds.

Sheol (sheol-s) wrote :

Okay I found the problem and the solution but it is still a bug.

my /etc/network/interfaces
was trying to bring up the device before it was ready and thus creating a bogus empty pid file.

By commenting essentially everything out of the file I got normal behavior back. (In this case I mean normal except that the netowork managers seem useless.)

That being said this is still clearly a bug.

chantra (chantra) wrote :

using /etc/network/interface , the devices will be brought up on boot up.
/etc/init.d/network restart
might be an easier workaround to your issue.

Removing everything from /etc/network/interfaces
will allow you to use networkmanager to configure and use your network.
Better option for roaming user.

Sheol (sheol-s) wrote :

Actually I haven't ever gotten knetwork manager or the one in gnome to ever do anything useful with a wireless card. In this case it doesn't see to see the networks which I see by simply running iwlist scan.

Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Using Hardy I have no problems at the moment. If I can remember correctly the latest updates of Gutsy solved the problem too as I can't remember the last time when I had to go through these kill/start sequences.

Thanks for the follow up. I'm closing this report due to your last comment regarding this being fixed with an update. If it's still an issue for the other submitters then don't hesitate to re-open.

Thanks for your time.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers