Wired network does not work after 8.10 upgrade

[Jerry Janes]

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.

[Colin Watson (cjwatson)]

I don't know where this really belongs, but choose-mirror definitely isn't it - that's a component of the installer that deals with mirror selection. Reassigning to network-manager for further analysis.

[Jerry Janes (jerry-janes)]

Colin,
  Thanks for moving it to network-manager. I tried to do that myself a
couple times and couldn't figure out how to do it. This is the first bug I
have logged and I was pretty sure I did it wrong. I will read more
Launchpad documentation before submitting more.

Thanks,
Jerry

----- Original Message -----
From: "Colin Watson" <email address hidden>
To: <email address hidden>
Sent: Tuesday, January 27, 2009 1:09 PM
Subject: [Bug 320268] Re: Wired network does not work after 8.10 upgrade

I don't know where this really belongs, but choose-mirror definitely
isn't it - that's a component of the installer that deals with mirror
selection. Reassigning to network-manager for further analysis.

** Changed in: network-manager (Ubuntu)
Sourcepackagename: choose-mirror => network-manager

--
Wired network does not work after 8.10 upgrade
https://bugs.launchpad.net/bugs/320268
You received this bug notification because you are a direct subscriber
of the bug.

Status in “network-manager” source package in Ubuntu: New

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 J...

[MattParkins (j-launchpad-the-parkins-co-uk)]

+1 - same thing happens to me with the latest version of the kernel in 8.10. I'm on recommended updates only and my wired networking only failed when I got the latest updates today. My 8.10 was working previously.

What happens is that it tries to connect (whether there is actually a cable in the wired slot or not - strange) and then just sits there trying to obtain an IP address which it never gets.

-m@

[MattParkins (j-launchpad-the-parkins-co-uk)]

Sorry, let me be much clearer about this. The problem came with an upgrade to the latest kernel or something that was updated with it. Its not a difference between 8.04 and 8.10 as my 8.10 was working just fine until this morning.

[MattParkins (j-launchpad-the-parkins-co-uk)]

I confirm it!

[Jerry Janes (jerry-janes)]

This happened to me when I upgraded a completely patched and working 8.04
installation to 8.10 I had no problem with 8.04 and have installed it on
three different machines. I also installed 8.10 from scratch and had the
same problem. I am using a wired network through a Belkin router to a cable
modem. After I got 8.10 working, I applied all the current patches and
tried removing the supersede nameserver from the dhclient.conf file. The
network did not work. I think something is getting messed up because of
router returning an IP rather than a actual name. This is what many routers
do by default.

[MattParkins (j-launchpad-the-parkins-co-uk)]

Hang on, so all 3 of us are using a belkin router then... ? Interesting...

[anton_es (anton-schnurer)]

hi, I'm using a dell netbook (911 first edition) dual boot xp & 8.10.
since I upgraded to the latest kernel delivered automatically through software update I can no longer connect to my wired connection AT ALL. It's exactly like described above, ONLY I got a LinkSys Router. Windows can connect, Linux the NM starts but times out and says that it doesn't get any IP-adress. Can I revert to an old kernel without problems ?
this is major annoying.
Wouldn't think that something like this is even possible.....ubuntu 8(!) and it can't connect to a router and get an IP adress ?

[Jerry Janes (jerry-janes)]

Anton,
  I don't know if switching the Kernel is a good idea or not. (I would
guess not.) It would be very interesting to check the /var/log/daemon.log
file to see if you have the same before and after differences I found.
(Search the file for the word namerserver.) If you do, you might try the
same hack I used in the /etc/dhcp3/dhclient.conf file. I am not a fixer but
just a reporter..... I am sure any information you can give will help
whoever fixes this problem.

[anton_es (anton-schnurer)]

it says
nameserver "192.168.0.1" although my router is on 192.168.1.1....
my dhclient.conf is empty, meaning everything is commented out.

[MattParkins (j-launchpad-the-parkins-co-uk)]

I did the "supersede nameserver 192.168.2.1" thing but to no avail (that is the correct gateway for me too).

The only workaround for me right now is booting into the previous kernel (-9). This is especially frustrating for me as wireless crashes the entire machine every few hours. Useless. Fedora time?

[anton_es (anton-schnurer)]

well, unfortunately I don't even have the old kernel. I was using wireless and after deciding that the new kernel seems stable I removed the old one. then I went home, connected to my wired network and vola .... nothing. I can't get it to see my router or get any IP from eth0.
I searched around and tried all the different dhclient commands, starting/stopping interfaces ... nothing...I'm lucky my neighbour has an unsecure wireless lan :) or I could not use the machine.
The same happens at work where we have Cisco routers with DHCP, my netbook worked without problems there before, so we can assume that it's not something the router does but rather the network manager doesn't do or know.

I tried the "supersede nameserver" option as well and it changed nothing.
let's hope for another update that miraculously solves this just liked it got broken.

[Jerry Janes (jerry-janes)]

Anton,
  Did you reboot after adding the supersede comand? It does not take effect
until the network is restarted or the system is rebooted. I found a reboot
was easier... In your case the suersede command should be: supersede
nameserver 192.168.0.1 (Do not put quotes around the IP address!)

[Jerry Janes (jerry-janes)]

I think maybe you and Anton have a different problem. I am using a wired
connection and my server never crashed it just did not connect to the
network. The supersede nameserver definately fixed the problem. I tried it
with and without it several times and it always worked with it and never
worked without it. After I was able to apply all current 8.10 updates I
tried with and without the supersede again. The network still did not work
without the command.

[anton_es (anton-schnurer)]

but my router is on 192.168.1.1, i will put this in and reboot.

[anton_es (anton-schnurer)]

nothing changed. here is some part of my daemon.log:

Feb 4 18:34:02 mini NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
Feb 4 18:34:02 mini NetworkManager: <info> (eth1): supplicant interface state change: 1 -> 2.
Feb 4 18:34:02 mini dhclient: Listening on LPF/eth0/00:21:70:af:8d:8c
Feb 4 18:34:02 mini dhclient: Sending on LPF/eth0/00:21:70:af:8d:8c
Feb 4 18:34:02 mini dhclient: Sending on Socket/fallback
Feb 4 18:34:02 mini dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Feb 4 18:34:05 mini gdmgreeter[5227]: Gtk-WARNING: Unable to locate theme engine in module_path: "ubuntulooks",
Feb 4 18:34:08 mini dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Feb 4 18:34:11 mini gdm[5012]: pam_sm_authenticate: Called
Feb 4 18:34:11 mini gdm[5012]: pam_sm_authenticate: username = [toni]
Feb 4 18:34:11 mini gdm[5012]: Error attempting to parse .ecryptfsrc file; rc = [-5]
Feb 4 18:34:11 mini gdm[5012]: Unable to read salt value from user's .ecryptfsrc file; using default
Feb 4 18:34:14 mini modprobe: WARNING: Error inserting padlock_aes (/lib/modules/2.6.27-11-generic/kernel/drivers/crypto/padlock-aes.ko): No such device
Feb 4 18:34:14 mini gdm[5012]: Mount of private directory return code [0]
Feb 4 18:34:19 mini dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Feb 4 18:34:28 mini x-session-manager[5289]: WARNING: Application 'libcanberra-login-sound.desktop' failed to register before timeout
Feb 4 18:34:31 mini dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Feb 4 18:34:44 mini dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Feb 4 18:34:47 mini NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it.
Feb 4 18:34:47 mini NetworkManager: <info> eth0: canceled DHCP transaction, dhcp client pid 5204
Feb 4 18:34:47 mini NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Feb 4 18:34:47 mini NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started...
Feb 4 18:34:47 mini NetworkManager: <info> (eth0): device state change: 7 -> 9
Feb 4 18:34:47 mini NetworkManager: <info> Marking connection 'Auto eth0' invalid.
Feb 4 18:34:47 mini NetworkManager: <info> Activation (eth0) failed.
Feb 4 18:34:47 mini NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
Feb 4 18:34:47 mini NetworkManager: <info> (eth0): device state change: 9 -> 3
Feb 4 18:34:47 mini NetworkManager: <info> (eth0): deactivating device (reason: 0).

[anton_es (anton-schnurer)]

ah, it seems it doesn't like the option in the dhclient.conf:

sudo dhclient

/etc/dhcp3/dhclient.conf line 53: no option named nameserver in space dhcp
supersede nameserver 192.
          ^
/etc/dhcp3/dhclient.conf line 53: semicolon expected.

^

but i did like described, i added the line
supersede nameserver 192.168.1.1
to the end of the file. so should i use '' to encase them and end it with an ; ?

[Jerry Janes (jerry-janes)]

Anton,
  You are 100% correct I apologize. However, I think you may have
discovered something. Below is my original dhclient.conf file. Everything
except the send host-name and the request is commented out. I put the
erroneous supersede command "before" the send host-name which I think would
have caused the rest of the script not to execute. If you put my "bad"
supersede at the end it would execute the send host-name and the request
command before the script failed. I rebooted using the original
dhclient.conf and my network didn't work. I decided to try commenting out
the send host-name and the request command. I rebooted and the network was
working! I do not understand at all why this works...

# Configuration file for /sbin/dhclient, which is included in Debian's
# dhcp3-client package.
#
# This is a sample configuration file for dhclient. See dhclient.conf's
# man page for more information about the syntax of this file
# and a more comprehensive list of the parameters understood by
# dhclient.
#
# Normally, if the DHCP server provides reasonable information and does
# not leave anything out (like the domain name, for example), then
# few changes must be made to this file, if any.
#

send host-name "<hostname>";
#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
netbios-name-servers, netbios-scope, interface-mtu;
#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/etc/dhcp3/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

#alias {
# interface "eth0";
# fixed-address 192.5.5.213;
# option subnet-mask 255.255.255.255;
#}

#lease {
# interface "eth0";
# fixed-address 192.33.137.200;
# medium "link0 link1";
# option host-name "andare.swiftmedia.com";
# option subnet-mask 255.255.255.0;
# option broadcast-address 192.33.137.255;
# option routers 192.33.137.250;
# option domain-name-servers 127.0.0.1;
# renew 2 2000/1/12 00:00:01;
# rebind 2 2000/1/12 00:00:01;
# expire 2 2000/1/12 00:00:01;
#}

[anton_es (anton-schnurer)]

after a last hal/network-manager update wired network does work again on dell mini9 / 2.6.27-11
but now wireless is not present anymore......aarrgh

[Thomas Hood (jdthood)]

Should be fixed in Ubuntu 12.04.