[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
presumably fixed in ubuntu-intrepid (nm 0.7) ** Changed in: network-manager (Ubuntu) Status: Confirmed = Fix Released -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
Because it doesn't happen on every configuration, I guess. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
I just tested the latest patch 0.6.5-0ubuntu16~pp3 (which is a fix for bug #145683), but I still have the same problem with dchp. I'm still getting the Old device activating, won't change messages during the DHCP requests. Could it be something to do with this, ie is nm receiving a valid response but ignoring them because it thinks eth0 is not fully activated? -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
I'm getting what might be a similar problem on Gutsy Ubuntu. It's not quite the same because NetworkManager connects fine to the wired network on eth0 normally when I reboot. BUT if I change eth0 to be manually configured and then change it back to 'roaming' mode, NetworkManager fails to get a DHCP-allocated address for eth0. This is also the case if I change it to be manually configured, reboot, and then change it back to roaming mode. I can, however, manually get an address with sudo dhclient eth0 (see in the log below at 09:13:01). I also have vmware installed and two virtual networks. My current ifconfig is (there's also a wireless eth1, which I disabled): eth0 Link encap:Ethernet HWaddr 00:0D:56:3C:1F:6D inet addr:10.2.1.227 Bcast:10.2.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4630 errors:0 dropped:0 overruns:0 frame:0 TX packets:3164 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1803229 (1.7 MB) TX bytes:625778 (611.1 KB) Interrupt:11 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1074 errors:0 dropped:0 overruns:0 frame:0 TX packets:1074 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:33423 (32.6 KB) TX bytes:33423 (32.6 KB) vmnet1Link encap:Ethernet HWaddr 00:50:56:C0:00:01 inet addr:192.168.156.1 Bcast:192.168.156.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:63 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vmnet8Link encap:Ethernet HWaddr 00:50:56:C0:00:08 inet addr:172.16.208.1 Bcast:172.16.208.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:64 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) and daemon.log shows NetworkManager trying without success to get an address, followed by dhclient successfully getting one: Oct 17 09:12:06 pegasus NetworkManager: info Will activate wired connection 'eth0' because it now has a link. Oct 17 09:12:06 pegasus NetworkManager: info SWITCH: no current connection, found better connection 'eth0'. Oct 17 09:12:06 pegasus NetworkManager: info Will activate connection 'eth0'. Oct 17 09:12:06 pegasus NetworkManager: info Device eth0 activation scheduled... Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) started... Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 1 of 5 (Device Prepare) started... Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) starting... Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) successful. Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. Oct 17 09:12:06 pegasus NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Oct 17 09:12:07 pegasus NetworkManager: info Activation (eth0) Beginning DHCP transaction. Oct 17 09:12:07 pegasus dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134519120 Oct 17 09:12:07 pegasus NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Oct 17 09:12:07 pegasus NetworkManager: info DHCP daemon state is now 12 (successfully started) for interface eth0 Oct 17 09:12:08 pegasus NetworkManager: info DHCP daemon state is now 1 (starting) for interface eth0 Oct 17 09:12:11 pegasus dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Oct 17 09:12:12 pegasus NetworkManager: info Old device 'eth0' activating, won't change. Oct 17 09:12:18 pegasus dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 Oct 17 09:12:18 pegasus NetworkManager: info Old device 'eth0' activating, won't change. Oct 17 09:12:28 pegasus last message repeated 2 times Oct 17 09:12:31 pegasus dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 Oct 17 09:12:34 pegasus NetworkManager: info Old device
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
Could you post your /etc/network/interfaces ? I had a similar problem, and cleaning up the file (just leaving lo instructions and auto eth1 / auto eth2) resolved it. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
This is the /etc/network/interfaces when NM is handling eth0, and with eth1 disabled: auto lo iface lo inet loopback auto eth1 #iface eth1 inet dhcp auto eth2 #iface eth2 inet dhcp auto ath0 #iface ath0 inet dhcp auto wlan0 #iface wlan0 inet dhcp When I configure NM to give eth0 a static address, it adds this: iface eth0 inet static address 10.1.1.11 netmask 255.0.0.0 auto eth0 Then when I change it back to use 'roaming' (ie managed by NM), it removes the reference to eth0. But it fails to get an address and eth0 stays on 10.1.1.11. Then when I do sudo dhclient eth0, I get a valid DHCP address. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
** Changed in: network-manager (Ubuntu) Status: Incomplete = Confirmed -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
does this still happen after a reboot? ** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium Status: New = Incomplete -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
Yes. It happens every time. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
Please stop NetworkMananger like: sudo /etc/dbu*/event*/25Network* stop then start it in a terminal like: sudo NetworkManager --no-daemon 21 | tee /tmp/nm.log and attach the nm.log file once network manager gave up. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
Here it is. Also, the dhclient command launched by NetworkManager is: (ps aux|grep dhclient) /sbin/dhclient -1 -lf /var/lib/dhcp3/dhclient.eth1.leases -pf /var/run/dhclient.eth1.pid -q -e dhc_dbus=31 -d eth1 And its output to /var/log/daemon.log is: Oct 16 11:52:30 herisson dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 Oct 16 11:52:37 herisson dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17 Oct 16 11:52:54 herisson dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 Oct 16 11:53:01 herisson dhclient: No DHCPOFFERS received. Fun fact: If I run the exact dhclient command launched by NetworkManager by hand (as root), it works! Oct 16 12:00:15 herisson dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 Oct 16 12:00:15 herisson dhclient: DHCPOFFER from 10.1.251.254 Oct 16 12:00:15 herisson dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Oct 16 12:00:15 herisson dhclient: DHCPACK from 10.1.251.254 Oct 16 12:00:15 herisson dhclient: bound to 10.1.250.214 -- renewal in 41567 seconds. ** Attachment added: networkmanager log http://launchpadlibrarian.net/10048809/nm.log -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
I just tested a wireless connection (eth2), and here DHCP works with NM. But still no luck with wired. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
After a grep -r eth0 /etc (and for eth1 and eth2) I noticed that VMWare was configured to bridge on eth1. The was updated since the last time I installed it ; I ran sudo vmware-config.pl again and now DHCP seems to be working again. Nevertheless, I don't understand why dhclient would fail to get the DHCPOFFER when launched by NM and not when launched from the terminal (with the same parameters !). I'm also not still not sure that VMWare was the cause of all this. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153219] Re: NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone
Woops, missing text: The KERNEL was updated since I installed VMWare. Sorry. -- NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalone https://bugs.launchpad.net/bugs/153219 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
