Should be fixed in Ubuntu 12.04.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/320268
Title:
Wired network does not work after 8.10 upgrade
Status in “network-manager” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: choose-mirror
I upgraded from 8.04.1 to 8.10 I have an old stupid Belkin firewall
router
This was from /var/log/daemon.log using 8.04.1
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> DHCP daemon state is now
4 (reboot) for interface eth0
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) scheduled...
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) started...
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> Retrieved the following
IP4 configuration from the DHCP daemon:
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> address 192.168.2.11
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> netmask 255.255.255.0
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> broadcast
255.255.255.255
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> gateway 192.168.2.1
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> nameserver 192.168.2.1
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> domain name 'ph.cox.net'
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) scheduled...
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) complete.
Jan 21 10:31:27 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) started...
This was from /var/log/daemon.log after upgrading to 8.10
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> DHCP: device eth0 state
changed preinit -> bound
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) scheduled...
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) started...
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> address 192.168.2.11
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> prefix 24
(255.255.255.0)
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> gateway 192.168.2.1
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> nameserver '192.168.2.1'
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> domain name 'ph.cox.net'
Jan 22 09:55:26 JANES-LINUX dhclient: bound to 192.168.2.11 -- renewal in
914840321 seconds.
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) scheduled...
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) complete.
Jan 22 09:55:26 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) started...
Jan 22 09:55:26 JANES-LINUX avahi-daemon[4771]: Joining mDNS multicast group
on interface eth0.IPv4 with address 192.168.2.11.
Jan 22 09:55:26 JANES-LINUX avahi-daemon[4771]: New relevant interface
eth0.IPv4 for mDNS.
Jan 22 09:55:26 JANES-LINUX avahi-daemon[4771]: Registering new address
record for 192.168.2.11 on eth0.IPv4.
Jan 22 09:55:27 JANES-LINUX NetworkManager: <info> (eth0): device state
change: 7 -> 8
Jan 22 09:55:27 JANES-LINUX NetworkManager: <WARN>
add_ip4_route_to_gateway(): Failed to add IPv4 default route on 'eth0': (-19)
Sucess
Jan 22 09:55:27 JANES-LINUX NetworkManager: <info> Policy set 'Auto eth0'
(eth0) as default for routing and DNS.
Jan 22 09:55:27 JANES-LINUX NetworkManager: <info> Activation (eth0)
successful, device activated.
Jan 22 09:55:27 JANES-LINUX NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) complete.
I noticed the network info displayed by NetworkManager was very
different. The thing I really noticed was the quotes around the
nameserver address in 8.10 and not 8.04.1
I was able to fix the problem by adding this to
/etc/dhcp3/dhclient.conf
# Added by Jerry
#supersede netmask 255.255.255.0
#supersede broadcast 255.255.255.255
supersede nameserver 192.168.2.1
# end Added by Jerry
After trial and error and numerous reboots I found the only thing
needed was the nameserver option. I do not know if the problem is
with dhclient or NetworkManager. I read through several problems in
the forum with 8.10 networking that might be the same as this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/320268/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
