Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I spent lot of time searching on my issue but no luck.
I have Debian installed a year ago, working perfectly until last week when network card connected to internet stopped to communicate. I did no change in configuration. It just stopped to work while I was reading an online web page. Network card connected to local network still works fine.
I thought it might be a NIC failure so I installed a new PCI NIC but no change, still no communication throught this NIC.
I verified/changed cable between NIC and the router, no luck. If I connect the same cable from router to a Windows PC, everything is OK. If I connect back to Debian machine, it does not work.
I tried connect this NIC with a different router with DHCP enabled, nothing, NIC will not communicate with DHCP server.
I tried to set static IP, no change.
Today I booted a Knoppix 6.2 and this NIC worked perfetly! It set up using DHCP, I could access the internet.
I booted machine as usual and the problem still persists of course.
This is information captured immediately after boot. The trouble NIC is eth0 after boot finishes.
# dmesg | grep eth
eth0: (PCI Express:2.5GB/s:Width x4) 00:15:17:6f:a1:b4
eth0: Intel(R) PRO/1000 Network Connection
eth0: MAC: 0, PHY: 4, PBA No: d50868-003
eth1: (PCI Express:2.5GB/s:Width x4) 00:15:17:6f:a1:b5
eth1: Intel(R) PRO/1000 Network Connection
eth1: MAC: 0, PHY: 4, PBA No: d50868-003
eth2: RTL8168b/8111b at 0xffffc20000032000, 00:1e:8c:1e:e4:19, XID 38000000 IRQ 316
udev: renamed network interface eth2 to eth0
udev: renamed network interface eth0_rename to eth2
bonding: bond0: enslaving eth1 as an active interface with a down link.
bonding: bond0: enslaving eth2 as an active interface with a down link.
eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
bonding: bond0: link status definitely up for interface eth2.
r8169: eth0: link up
One more information on one of the tests I have done. I connected my notebook using cross-over ethernet cable to eth0 and on both sides set static IP. This was the only configuration that worked - receiving and transmitting worked well.
When I connect eth0 to internet router, there is no communication and especialy there are no RX bytes, just couple of TX when I tried to ping default gateway. I thought the router may be faulty hence I tried brand new wifi router with DHCP server enabled - no communication between eth0 and DHCP router as well. This wifi router's DHCP server works fine when connected to my notebook...
Ok. According to hwinfo you have only one ethernet card: "RTL8111/8168B PCI Express Gigabit Ethernet controller"
Device File: eth0
Driver: "r8169"
Driver Status: r8169 is active
Driver Activation Cmd: "modprobe r8169"
Can you connect that ethernet card to router with straight cable, make sure that LED start blinking on both sides, and then do "dmesg | tail" and "ifconfig eth0"
Post output here please.
LEDs on both sides lit on although only the status link. Traffic LEDs are not blinking.
Actualy there are eth1 and eth2 bonded as bond0, see my first post with /etc/network/interfaces content. bond0 is for local network and works fine. If cancel bonding and reset eth1 and eth2 for dynamic settings and connect them to a router with DHCP enabled, it behaves the same. Link comes up but NIC gets no configuration from DHCP and there is no traffic.
I started to install Debian on new harddrive. I forgot to copy some things from old installation so I reconnected old harddrive. Network card works without a problem. I did no SW/HW change in setup. I hope this will not happen in future.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.