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 me
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.
--
ubunt
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 respons
** 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 fo
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 ad
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 thi
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 DHC
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
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 fo
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, whi
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: DHCPDISCOVE
Please stop NetworkMananger like:
sudo /etc/dbu*/event*/25Network* stop
then start it in a terminal like:
sudo NetworkManager --no-daemon 2>&1 | tee /tmp/nm.log
and attach the nm.log file once network manager gave up.
--
NetworkManager on Gutsy: No DHCPOFFERS - but dhclient working standalo
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
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
14 matches
Mail list logo
