NM can't connect via DSL modem on Ethernet port -- RealTek RTL-8029(AS) ne2k-pci

[Yves Dony]

I'm using a DSL modem connected through an Ethernet port to connect to the internet.
It used to work smoothly with Gutsy, Hardy and Intrepid but it hasn't been set up correctly during the upgrade to Jaunty and the automatic installation of Network Manager (I didn't use NM with previous versions).

Initially there were no connections defined in Network Manager and "Wired - Device not managed" appeared in gray when right-clicking on the NM-applet icon.
I tried to solve it by changing managed=false to managed=true in /etc/NetworkManager/nm-system-settings.conf
Thereafter Network Manager automatically detected eth1 and the DSL connection but it's still unable to connect; I always receive the message "Wired Network disconnected - you're now working offline" on a black background.

Hereafter some further information:

sudo lshw -C network
  *-network
       description: Ethernet interface
       product: 3c940 10/100/1000Base-T [Marvell]
       vendor: 3Com Corporation
       physical id: 5
       bus info: pci@0000:02:05.0
       logical name: eth1
       version: 12
       serial: 00:0c:6e:40:4c:04
       size: 10MB/s
       capacity: 1GB/s
       width: 32 bits
       clock: 66MHz
       capabilities: pm vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=skge driverversion=1.13 duplex=half firmware=N/A latency=64 link=yes maxlatency=31 mingnt=23 module=skge multicast=yes port=twisted pair speed=10MB/s
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: pan0
       serial: 3a:e1:6c:84:2d:e2
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

ifconfig
eth1 Link encap:Ethernet HWaddr 00:0c:6e:40:4c:04
          inet6 addr: fe80::20c:6eff:fe40:4c04/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:458 (458.0 B) TX bytes:3848 (3.8 KB)
          Interrupt:22

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:848 errors:0 dropped:0 overruns:0 frame:0
          TX packets:848 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:67488 (67.4 KB) TX bytes:67488 (67.4 KB)

dmesg | grep eth
[ 1.739081] Driver 'sd' needs updating - please use bus_type methods
[ 1.739098] Driver 'sr' needs updating - please use bus_type methods
[ 3.818844] skge eth0: addr 00:0c:6e:40:4c:04
[ 9.771834] udev: renamed network interface eth0 to eth1
[ 32.913429] skge eth1: enabling interface
[ 32.917093] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 35.180253] skge eth1: Link is up at 10 Mbps, half duplex, flow control none
[ 35.180454] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 45.480009] eth1: no IPv6 routers present

cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto dsl-provider
iface dsl-provider inet ppp
pre-up /sbin/ifconfig eth1 up # line maintained by pppoeconf
provider dsl-provider

auto eth1
iface eth1 inet manual

cat /etc/NetworkManager/nm-system-settings.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true

[Ayon Khan (ayonkhan)]

Same problem here. :( But I did't upgrade from Intrepid to Jaunty. I directly install from CD (Jaunty).

[SabreWolfy (sabrewolfy)]

I can confirm that something is definitely wrong with wired (at least) connectivity in Jaunty. Did not experience this in Gutsy, Hardy or Intrepid. I have three desktop machines which are connected by wire to the Internet. Over the last few days, each one of these has disconnected from the 'net and is dead in the water. Of course, I can't SSH in to restart them, so I need to get physical access to them. Here is what I found in syslog:

May 4 03:37:40 XXX NetworkManager: <info> DHCP: device eth0 state changed renew -> expire
May 4 03:37:40 XXX dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
May 4 03:37:40 XXX NetworkManager: <info> DHCP: device eth0 state changed expire -> preinit
May 4 03:37:45 XXX dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
May 4 03:37:50 XXX dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
May 4 03:38:00 XXX dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
May 4 03:38:11 XXX dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
May 4 03:38:22 XXX dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
May 4 03:38:32 XXX dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
May 4 03:38:41 XXX dhclient: No DHCPOFFERS received.
May 4 03:38:41 XXX dhclient: No working leases in persistent database - sleeping.
May 4 03:38:41 XXX NetworkManager: <info> DHCP: device eth0 state changed preinit -> fail
May 4 03:38:41 XXX NetworkManager: <info> (eth0): device state change: 8 -> 9
May 4 03:38:41 XXX NetworkManager: <info> Marking connection 'Auto eth0' invalid.
May 4 03:38:41 XXX NetworkManager: <info> Activation (eth0) failed.
May 4 03:38:41 XXX NetworkManager: <info> (eth0): device state change: 9 -> 3
May 4 03:38:41 XXX NetworkManager: <info> (eth0): deactivating device (reason: 0).

It seems that something goes wrong when the IP address is being renewed? I think this only happens on idle connections.

[Yves Dony (yves-dony)]

The issue seems not to be directly related to Network-Manager but rather to the RP-PPPoE plugin.

I uninstalled Network-Manager, installed Wicd instead, and issued the "sudo pon dsl-provider" command; I am connected now and the connection appears to be stable up to now (about 7 hours total connection time).

I remember I had to install something (probably the equivalent plugin) when setting up Ubuntu (Gutsy) on my computer for the first time but I didn't had to do it again after upgrading to Hardy or Intrepid. Also I must now use the command each time I startup my computer; what should I do to make it be loaded automatically at startup ?

Also, I don't think Wicd is actually working it always indicates "Not connected" in its stauts bar.

Updated additionnal information:

sudo lshw -C network
  *-network
       description: Ethernet interface
       product: 3c940 10/100/1000Base-T [Marvell]
       vendor: 3Com Corporation
       physical id: 5
       bus info: pci@0000:02:05.0
       logical name: eth1
       version: 12
       serial: 00:0c:6e:40:4c:04
       size: 10MB/s
       capacity: 1GB/s
       width: 32 bits
       clock: 66MHz
       capabilities: pm vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=skge driverversion=1.13 duplex=half firmware=N/A latency=64 link=yes maxlatency=31 mingnt=23 module=skge multicast=yes port=twisted pair speed=10MB/s
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: pan0
       serial: 72:84:05:c0:75:4a
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

ifconfig
eth1 Link encap:Ethernet HWaddr 00:0c:6e:40:4c:04
          inet6 addr: fe80::20c:6eff:fe40:4c04/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:24885 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21057 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28856170 (28.8 MB) TX bytes:5761864 (5.7 MB)
          Interrupt:22

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:404 errors:0 dropped:0 overruns:0 frame:0
          TX packets:404 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:32272 (32.2 KB) TX bytes:32272 (32.2 KB)

ppp0 Link encap:Point-to-Point Protocol
          inet addr:81.247.69.102 P-t-P:81.247.69.1 Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
          RX packets:24516 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20683 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:28195065 (28.1 MB) TX bytes:5200001 (5.2 MB)

dmesg | grep eth
[ 1.743053] Driver 'sd' needs updating - please use bus_type methods
[ 1.743069] Driver 'sr' needs updat...

[Yves Dony (yves-dony)]

Found the solution: I had to use the "sudo pppoeconf" command.

Pending questions:
1. Why hasn't it been set up correctly while upgrading to Jaunty ?
2. Why is it documented for previous versions only (up to Intrepid)?

[SabreWolfy (sabrewolfy)]

I tried the fix suggested in the link below and I'm waiting to see if it fixed the problem.

http://www.prash-babu.com/2009/05/how-to-fix-ip-by-dhcp-issue-in-ubuntu.html

[SabreWolfy (sabrewolfy)]

I can confirm that my desktop machine running Jaunty is affected by this, but the machine running Jaunty Server does not appear to be affected.

[aslam karachiwala (akwala)]

Intrepid amd64 -- Suddenly lost wired (and wireless) networking -- NM lists "Auto eth0", which corresponds to my wired network interface, but times out when acquiring an IP.

I upgraded to Jaunty, hoping that that would fix the issue, but no such luck.

I tried deleting "rfc3442" from /etc/dhcp3/dhclient.conf as suggested at the link that SabreWolfy posted above; it doesn't seem to have made any difference.

I'm attaching my networking info -- lshw, lspci, ifconfig.

[Ayon Khan (ayonkhan)]

Updating Kernel fixed this issue. :)

[aslam karachiwala (akwala)]

Re my comment above -- https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/368709/comments/7 --

The apparent culprit was my router -- wired connections from it were failing, while it worked fine for wireless. Upon replacing the router I was able to get wired connection working via NM.

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version (10.04), this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 368709, and any other logs that are relevant for this particular issue.

[Yves Dony (yves-dony)]

I upgraded to lucid last light and I didn't experience any problem with
my internet connection (the problem still appeared with karmic).
I will try to find time to provide updated logs.
Thank you for your message.

On 04/09/2010 05:08 PM, Przemysław Kulczycki wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. We are sorry that we do not always have the capacity to
> look at all reported bugs in a timely manner. There have been many
> changes in Ubuntu since that time you reported the bug and your problem
> may have been fixed with some of the updates. If you could test the
> current Ubuntu development version (10.04), this would help us a lot. If
> you can test it, and it is still an issue, we would appreciate if you
> could upload updated logs by running apport-collect 368709, and any
> other logs that are relevant for this particular issue.
>

[serola (sami-serola)]

Unfortunately having this issue with A-link V100AP VDSL2 router/modem. Other ADSL routers works just alright, but this V100AP does not give me IP on Eee PC901 running Ubuntu 10.04 Netbook Finnish Remix.

I can even login into wireless why I'm sure the PC is connected to router but then it just can't get through. I have tried to comment out "rfc3442" and even mask the device to Microsoft like explained here:
https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/94359

Running out of ideas. So, any suggestion would be welcome.

P.S. A-link V100AP should run just fine with Linux OS and it does with Windows.

[Robert Neuron (luddism)]

I need to know what hardware I have and if it is working. Specifically, every time I try to upgrade from 11.10 to 12.04, I lose my internet connection and have to do a clean install of 11.10 when the connection magically reappears. I have tried the upgrade page on the Software Center and the Alternate CD(my computer won't accept the live CD)all the while trying to select to keep my current settings. My driver is ne2k-pci which is supposed to work with 12.04. Here is what I have on 11.10 which works and I forgot to run it when I installed 12.04.

sudo lshw -C network
  *-network
       description: Ethernet interface
       product: RTL-8029(AS)
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 10
       bus info: pci@0000:00:10.0
       logical name: eth0
       version: 00
       serial: 00:00:e8:e9:6c:29
       width: 32 bits
       clock: 33MHz
       capabilities: ethernet physical
       configuration: broadcast=yes driver=ne2k-pci driverversion=1.03 ip=192.168.1.91 latency=0 multicast=yes
       resources: irq:10 ioport:d000(size=32)

[Thomas Hood (jdthood)]

> I upgraded to lucid last light and I didn't experience any problem with my internet connection

Thanks for the update.