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) -- [jaunty] can't connect via dhcp https://bugs.launchpad.net/bugs/312157 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
