Network wired connection suddenly stopped working (wheezy)

[larissa]

I've got a problem with the network connection on debian wheezy and I can't possibly figure out what it is. The network connection worked fine until a few weeks ago when the machine was moved, then it just doesn't connect to the wired network anymore. It's the same network, the pc is just on a diferent table, and the cable is fine since I'm posting this right now with my laptop plugged on it.

Some information I gathered:

/etc/network/interfaces

Code: Select all

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

/etc/NetworkManager/NetworkManager.conf

Code: Select all

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

The Network Manager used to say "the wired connection is unmanaged", then I read this Debian Wiki , commented the last line in interfaces, stopped and started the networking and network-manager services, runned dhclient on terminal and it worked, I was able to ping my router, other machines, internet was working... I thought I had solved my problem so I shutdown the pc. When I turned it on again, I had no network wired connection once more. I tried to restart the sevices, recheck my previous steps (and then retried with managed=true and uncommented the line in interfaces), tried to do ifdown/up eth0, runned dhclient, but nothing worked. It was days ago, I tried it again, and other things I googled too, but so far nothing works and I haven't been able to connect ever since

Here is the atual state of my config files:

Code: Select all

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp

Code: Select all

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

Since the Network Manager is managing the connections, it doesn't say unmanaged anymore, instead it says "cabe unplugged". (and there's no need to ask, I checked and the cable is plugged =P )
Everytime I run dhclient, it can't get a lease and in dmesg I can see a "eth0: link is not ready" message. I assumed is not a configuration problem in my router (other machines works just fine).

The kernel version is 3.1.0-1-686-pae and here some commands returns that may help:

lspci | grep Ether

Code: Select all

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

lspci -v

Code: Select all

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
	Subsystem: Realtek Semiconductor Co., Ltd. TEG-ECTX Gigabit PCI-E Adapter [Trendnet]
	Flags: bus master, fast devsel, latency 0, IRQ 42
	I/O ports at e800 [size=256]
	Memory at febff000 (64-bit, non-prefetchable) [size=4K]
	Memory at fdff0000 (64-bit, prefetchable) [size=64K]
	Expansion ROM at febc0000 [disabled] [size=128K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [70] Express Endpoint, MSI 00
	Capabilities: [b0] MSI-X: Enable- Count=2 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 18-00-00-00-68-4c-e0-00
	Kernel driver in use: r8169

modinfo r8169

Code: Select all

filename:       /lib/modules/3.1.0-1-686-pae/kernel/drivers/net/r8169.ko
firmware:       rtl_nic/rtl8105e-1.fw
firmware:       rtl_nic/rtl8168e-3.fw
firmware:       rtl_nic/rtl8168e-2.fw
firmware:       rtl_nic/rtl8168e-1.fw
firmware:       rtl_nic/rtl8168d-2.fw
firmware:       rtl_nic/rtl8168d-1.fw
version:        2.3LK-NAPI
license:        GPL
description:    RealTek RTL-8169 Gigabit Ethernet driver
author:         Realtek and the Linux r8169 crew <netdev@vger.kernel.org>
srcversion:     3E842CC3B34475192563328
alias:          pci:v00000001d00008168sv*sd00002410bc*sc*i*
alias:          pci:v00001737d00001032sv*sd00000024bc*sc*i*
alias:          pci:v000016ECd00000116sv*sd*bc*sc*i*
alias:          pci:v00001259d0000C107sv*sd*bc*sc*i*
alias:          pci:v00001186d00004302sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008168sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008167sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008136sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008129sv*sd*bc*sc*i*
depends:        mii
intree:         Y
vermagic:       3.1.0-1-686-pae SMP mod_unload modversions 686 
parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
parm:           debug:Debug verbosity level (0=none, ..., 16=all) (int)

dmesg

Code: Select all

[   13.824021] r8169 0000:02:00.0: eth0: link down
[   13.824027] r8169 0000:02:00.0: eth0: link down
[   13.824143] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.566508] Bluetooth: Core ver 2.16
[   17.566522] NET: Registered protocol family 31
[   17.566524] Bluetooth: HCI device and connection manager initialized
[   17.566526] Bluetooth: HCI socket layer initialized
[   17.566527] Bluetooth: L2CAP socket layer initialized
[   17.566531] Bluetooth: SCO socket layer initialized
[   17.608358] Bluetooth: RFCOMM TTY layer initialized
[   17.608362] Bluetooth: RFCOMM socket layer initialized
[   17.608363] Bluetooth: RFCOMM ver 1.11
[   17.677706] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   17.677708] Bluetooth: BNEP filters: protocol multicast
[   18.315042] lp0: using parport0 (interrupt-driven).
[   18.529696] ppdev: user-space parallel port driver
[   31.555215] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
[ 1296.840101] r8169 0000:02:00.0: PCI INT A disabled
[ 1477.267815] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1477.267845] r8169 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1477.267876] r8169 0000:02:00.0: setting latency timer to 64
[ 1477.267924] r8169 0000:02:00.0: irq 42 for MSI/MSI-X
[ 1477.268931] r8169 0000:02:00.0: eth0: RTL8168c/8111c at 0xf8216000, 70:71:bc:46:da:57, XID 1c4000c0 IRQ 42
[ 1477.278378] r8169 0000:02:00.0: eth0: link down
[ 1477.278383] r8169 0000:02:00.0: eth0: link down
[ 1477.279124] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1517.290452] r8169 0000:02:00.0: eth0: link down
[ 1517.290457] r8169 0000:02:00.0: eth0: link down
[ 1517.290655] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4990.637743] r8169 0000:02:00.0: eth0: link down
[ 4990.637748] r8169 0000:02:00.0: eth0: link down
[ 4990.638030] ADDRCONF(NETDEV_UP): eth0: link is not ready

ifconfig

Code: Select all

eth0      Link encap:Ethernet  Endereço de HW 70:71:bc:46:da:57  
          UP BROADCASTMULTICAST  MTU:1500  Métrica:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          colisões:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          IRQ:42 Endereço de E/S:0x6000 

lo        Link encap:Loopback Local  
          inet end.: 127.0.0.1  Masc:255.0.0.0
          endereço inet6: ::1/128 Escopo:Máquina
          UP LOOPBACKRUNNING  MTU:16436  Métrica:1
          RX packets:498 errors:0 dropped:0 overruns:0 frame:0
          TX packets:498 errors:0 dropped:0 overruns:0 carrier:0
          colisões:0 txqueuelen:0 
          RX bytes:53554 (52.2 KiB)  TX bytes:53554 (52.2 KiB)

dhclient eth0 -d

Code: Select all

Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/70:71:bc:46:da:57
Sending on   LPF/eth0/70:71:bc:46:da:57
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I started suspecting it could be a driver problem, but according to this bug report the module version I'm using as seen in modinfo and my kernel version is supposed to work.

I've searched here and googled about it but nothing worked in my situation.
This has been bugging me for days, maybe i'm missing something in the network configuration. It's just that I've tried everything I could think of.

Any help is truly aprecieted.

[BowCatShot]

Get yourself a brand new known good cable and replace the old one. I' ve had what you're describing happen many times due to a faulty cable that worked ok in one position but, when moved or rearranged, stopped working.

[mslinux]

I'm using the same chip on my laptop without problem ( I'm on Squeeze with backports of 3.2 kernel amd64 )
Perhaps, try using 3.2 kernel, if that does not work, maybe you are experiencing this issue :
http://forums.debian.net/viewtopic.php?f=6&t=75299

[cynwulf]

Since the Network Manager is managing the connections, it doesn't say unmanaged anymore, instead it says "cabe unplugged". (and there's no need to ask, I checked and the cable is plugged =P )

The cable may be plugged in, but are the link and activity (amber/green) LEDs also lit up?

[larissa]

The cable may be plugged in, but are the link and activity (amber/green) LEDs also lit up?

I think they don't lit up. I'm gonna have to check tomorrow. Would that mean is a cable problem as BowCatShot suggested?
I'm going to plug a new cable tomorrow and update this with the results. Also thanks mslinux for the link, I'll check it out after testing the cable again.

Edit:

I just checked and the LEDs really don't lit up. However, during boot the activity (amber) led did lit up and then went off on login screen.
I also tried with a brand new cable without success
Does that indicate a NIC problem? I still can connect using the same cable with my laptop

[cynwulf]

Add the non-free repo (may as well add contrib also) run "aptitude update" and install firmware-realtek. It's required for that NIC to work.

e.g.

Code: Select all

deb http://ftp.uk.debian.org/debian/ testing main
deb-src http://ftp.uk.debian.org/debian/ testing main

Code: Select all

deb http://ftp.uk.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.uk.debian.org/debian/ testing main contrib non-free

[aspnair]

Install the package "ethtool" and when you have problem do
ethtool eth0
See Link is up and the current speed etc.