[jaunty] can't connect via dhcp

[Nizar Kerkeni]

After today updates (linux-*-2.6.28.4.4 and wpasupplicant 0.6.6-2) on jaunty alpha 2 amd64 version. It's impossible to connect to my DHCP server with wired and wireless network. I have to configure a manual setting for eth0 to be connected.
Log trace

Dec 29 14:30:36 jaunty dhclient: Internet Systems Consortium DHCP Client V3.1.1
Dec 29 14:30:36 jaunty dhclient: Copyright 2004-2008 Internet Systems Consortium.
Dec 29 14:30:36 jaunty dhclient: All rights reserved.
Dec 29 14:30:36 jaunty dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Dec 29 14:30:36 jaunty dhclient:
Dec 29 14:30:36 jaunty dhclient: wmaster0: unknown hardware address type 801
Dec 29 14:30:37 jaunty dhclient: wmaster0: unknown hardware address type 801
Dec 29 14:30:37 jaunty dhclient: Listening on LPF/eth0/XX:XX:XX:XX:XX:XX
Dec 29 14:30:37 jaunty dhclient: Sending on LPF/eth0/XX:XX:XX:XX:XX:XX
Dec 29 14:30:37 jaunty dhclient: Sending on Socket/fallback
Dec 29 14:30:37 jaunty dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Dec 29 14:30:45 jaunty dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Dec 29 14:30:59 jaunty dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Dec 29 14:31:08 jaunty dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Dec 29 14:31:19 jaunty dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Dec 29 14:31:27 jaunty dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Dec 29 14:31:36 jaunty dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Dec 29 14:31:38 jaunty dhclient: No DHCPOFFERS received.

[Nizar Kerkeni (nizarus)]

All is ok now !!
strange.

[Gregor (aguafuertes)]

My bug matches the description from above:

- installed Jaunty beta on Laptop (Lenovo X300, Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection, Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection)

- wireless and wired network connections work out of the box at home, both DHCP

- used laptop at work, wired connection works perfect with DHCP

- use Laptop again at home, no wireless or wired connection via DHCP. Manually configured connection works

- I installed no Updates in between, just Samba. This might be of interest because of the output I get when no DHCPOFFERS are received, see below...

Otherwise, the output is very similar to the original reporter's when running sudo dhclient or checking the syslog:

Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:21:5c:54:5d:25
Sending on LPF/wlan0/00:21:5c:54:5d:25
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Listening on LPF/eth0/00:1f:e2:18:d1:51
Sending on LPF/eth0/00:1f:e2:18:d1:51
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
 * Reloading /etc/samba/smb.conf smbd only
   ...done.

[Gregor (aguafuertes)]

I just attached a syslog excerpt, showing what happens when I try to activate a wireless connection via Networkmanager.

[Gregor (aguafuertes)]

And just like with the original reporter, things work again. I rebooted the laptop and the router serveral times, and now DHCP works again, without changing any seetings are installing any updates.

This is especially strange as I could connect via DHCP with an old Laptop running Intrepid the whole time.

The output from running dhclient looks as follows, the strange wmaster0 message remains:

sudo dhclient
[sudo] password for aguafuertes:
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Listening on LPF/eth0/00:1f:e2:18:d1:51
Sending on LPF/eth0/00:1f:e2:18:d1:51
Listening on LPF/wlan0/00:21:5c:54:5d:25
Sending on LPF/wlan0/00:21:5c:54:5d:25
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPOFFER of 192.168.1.101 from 192.168.1.1
DHCPREQUEST of 192.168.1.101 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.101 from 192.168.1.1
 * Reloading /etc/samba/smb.conf smbd only
   ...done.
bound to 192.168.1.101 -- renewal in 36447 seconds.

[Dominik Tritscher (dominik-tritscher)]

I experience exactly the same behaviour using a notebook with a SiS network card. The problem only occurs in our corporate network using the wired network. Wireless works fine.
My syslog looks quite the same as above so I didn't reposte it. Rebooting, reconfiguring the dhcp-packages and updating didn't help (running jaunty).
What additional info can I provide to help tracking down that issue?

[Ype (ykingma)]

I have a slightly different problem with dhcp after upgrading from 8.10 to 9.04 yesterday.

After boot using the default kernel there is no wired connection to the internet, but everything on the local network is available. (ping by name to local machines works, but pop for email fails.)
If I did not have another machine on the local network, I would have had no way to know how to fix this, as this isolates the upgraded machine from the internet.

I can always correct this by doing:

sudo ifdown eth0
sudo ifup eth0

Since this is repeatable, I'd like to hunt it down to the source of the problem, but I have no idea how to proceed.

The network icon in the system tray does not show an active network (neither wired nor wireless) before and after the ifdown/ifup fix.

Any suggestions as to what I could do to fix this?

[Ype (ykingma)]

A workaround for my problem is to add the following two lines to /etc/rc.local boot script just before the final exit 0 line:

ifdown eth0
ifup eth0

Doing this has the commands are executed at boot up.

Still, I'd like to help in hunting this down, just leave a message here.

[jonj (jonjackson)]

I believe I have the same issue as Ype. My fresh jaunty install was working fine until some point recently when it can't connect to anything outside the local network.

Ping works locally, but ping www.ubuntu.com gives 'connect: Network is unreachable'
DHCP lookups are working, via the router, so host www.ubuntu.com gives a correct ip address

I have two other machines connected to the same router (Debian etch and MacOS) and both connect to the internet ok.

[jonj (jonjackson)]

I forgot to add in the previous post:

'ifdown eth0' returns 'Ignoring unknown interface eth0=eth0',

'route' returns
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0

[Ype (ykingma)]

I have also reported this via ubuntu-bug, in that way it got bug number 374006

[Rafac24 (cabanas86)]

I am having the exact same issue and I cant find the solution. I am using a Broadcom WIreless BCM 4312 in a Dell XPS M1330. The issue used to happen only sometimes when i first installed Jaunty, but now i cannot connect to the internet permanently. I have had to use Vista for the past few days. I do not understand how this can be happening, as I had no problems with networking on Intrepid.
I have tried the ifup/if down commands and they both return the error "Ignoring unknown interface=eth0"

I have a suspicion that it has to do with the wireless card because my father also upgraded to Jaunty and has not had any networking issues. He's running an older Dell B130 with Intel PROWireless card.

[Rafac24 (cabanas86)]

This is what finally worked for me:
http://ubuntuforums.org/showpost.php?p=7276275&postcount=8

I do not understand the reason why it works, but my internet is back. This seems to be a temporary fix...I hope it will be permanently fixed in the future.

[^_Pepe_^ (jose-angel-fernandez-freire)]

This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest Karmic 9.10 release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/ .

If the issue remains, could you run the following command from a
Terminal (Applications->Accessories->Terminal) while running Karmic. It
will automatically gather and attach updated debug information to this
report.

apport-collect -p linux 312157

[Bjoern Hurling (bbxxx)]

Hi,

looks like the problem is still there. But for me it is slightly different:

The first DHCP that's started on cable plug in fails. But second, manually started, DHCP succeeds. This is how I reproduce the bug:
if I plug in my ethernet cable, dhcp is started by NetworkManager but fails. The output in syslog contains the well-known DHCPDISCOVER lines (5 times).

Jan 27 11:27:31 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jan 27 11:27:36 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jan 27 11:27:43 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Jan 27 11:27:52 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Jan 27 11:28:05 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9

NetworkManager stops DHCP transaction and deactivates the device:

Jan 27 11:28:14 laptop NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it.
Jan 27 11:28:14 laptop NetworkManager: <info> eth0: canceled DHCP transaction, dhcp client pid 5553
Jan 27 11:28:14 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Jan 27 11:28:14 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started...
Jan 27 11:28:14 laptop NetworkManager: <info> (eth0): device state change: 7 -> 9
Jan 27 11:28:14 laptop NetworkManager: <info> Marking connection 'Auto eth0' invalid.
Jan 27 11:28:14 laptop NetworkManager: <info> Activation (eth0) failed.
Jan 27 11:28:14 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
Jan 27 11:28:14 laptop NetworkManager: <info> (eth0): device state change: 9 -> 3
Jan 27 11:28:14 laptop NetworkManager: <info> (eth0): deactivating device (reason: 0).

Now I can left-click on the NetworkManagerApplet and select my device (eth0). This time NetworkManager re-activates the device and the DHCP request succeeds.

As far as I can tell, the first 5 DHCPREQUESTs never reached the DHCP server. On the other hand, I even Wireshark to capture the interface output on eth0: the first five REQUESTs show up but it seems as if the packets are never really sent to the wire.

This is my Ethernet controller: Broadcom Corporation NetXtreme BCM5753M Gigabit Ethernet PCI Express (rev 21)

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]