My firewall (FC1) had a 3COM 3c900B and a 3c905b, the former being the outside interface and only running at 10/half. I was seeing collisions that were making my VoIP run poorly, so I decided to swap it out with another 3c905b. And, for some reason, mii-tool reported eth0 as always having no link status, the interface never showed as RUNNING, and I had to ifconfig eth0 UP manually all the time, but it worked.
I replaced the 900b with the 905 and it didn't work. The interface showed up and was detected, but I couldn't get a DHCP address. Kudzu found it though.
Long story short, I even went so far as replacing both cards with intel e100s, but the same behaviour was seen for the card in eth0. No link, no DHCP, -UP -RUNNING. No matter which card was eth0, no matter which interrupt I had it on.
Finally, I put 3 NICs in and am running off of eth1/eth2 and it works fine.
I have no clue why this is happening. I wiped any trace of network stuff in /etc/mod*, rebuilt the initrd, and grepped under /etc for any mention of eth0. It even does this in single user mode. No kernel paramaters either, and I'm running the latest FC1 kernel from Legacy.
Any idea where else to look for this configuration?
Thanks,
Sean
On 11 Nov, Sean A. Walberg wrote:
I have no clue why this is happening. I wiped any trace of network stuff in /etc/mod*, rebuilt the initrd, and grepped under /etc for any mention of eth0. It even does this in single user mode. No kernel paramaters either, and I'm running the latest FC1 kernel from Legacy.
What are you using to configure the card? Did you look in /etc/sysconfig/network-scripts/ifcfg-eth0? Make sure there is no IPADDR set and you have BOOTPROTO=dhcp. In fact, besides DEVICE, BOOTPROTO, ONBOOT and TYPE you might want to delete all other entries, espcially HWADDR. Then ifdown/ifup and it should work. ifcfg-eth0 controls the whole enchilada and it's got to be something in there, assuming your modules are ok, which appears to be the case.
On Sun, 13 Nov 2005, Trevor Cordes wrote:
On 11 Nov, Sean A. Walberg wrote:
I have no clue why this is happening. I wiped any trace of network stuff in /etc/mod*, rebuilt the initrd, and grepped under /etc for any mention of eth0. It even does this in single user mode. No kernel paramaters either, and I'm running the latest FC1 kernel from Legacy.
What are you using to configure the card? Did you look in
Kudzu (ie network-config), and editing ifcfg-eth0.
/etc/sysconfig/network-scripts/ifcfg-eth0? Make sure there is no IPADDR set and you have BOOTPROTO=dhcp. In fact, besides DEVICE, BOOTPROTO, ONBOOT and TYPE you might want to delete all other entries, espcially HWADDR. Then ifdown/ifup and it should work. ifcfg-eth0 controls the whole enchilada and it's got to be something in there, assuming your modules are ok, which appears to be the case.
Nope, it's clean. Part of my final fix was to put ONBOOT=no in ifcfg-eth0 so the boot process wouldn't bother with the card on boot.
mii-tool shows no link status (nor does the switch), even after I manually ifconfig the interface to be UP/RUNNING.
Sean
Nope, it's clean. Part of my final fix was to put ONBOOT=no in ifcfg-eth0 so the boot process wouldn't bother with the card on boot.
mii-tool shows no link status (nor does the switch), even after I manually ifconfig the interface to be UP/RUNNING.
Huh? The switch shows no link? That makes me think: bad cable, bad NIC. Perhaps try a different PCI slot? I wouldn't use the one directly next to the AGP or the last (bottom) one if you can help it.
What happens if eth0 is a different chipset card (ie: a different module)... try a RT8139 or similar -- they always work.
Email me your ifcfg-eth0 and modprobe.conf if that doesn't help.
On Mon, 14 Nov 2005, Trevor Cordes wrote:
Huh? The switch shows no link? That makes me think: bad cable, bad NIC. Perhaps try a different PCI slot? I wouldn't use the one directly next to the AGP or the last (bottom) one if you can help it.
Tried different cable. Different PCI slots, different card (3c509b and E100). And if I play with my modules.conf to make a different card eth0, whichever card is eth0 has the problem.
What happens if eth0 is a different chipset card (ie: a different module)... try a RT8139 or similar -- they always work.
I don't have one handy. The only card that's ever seemed to work at eth0 is that older 3COM one (not at home now, can't think of the model), but even it had problems. I've cycled through 5 ethernet cards (the old one, two 3c905b's, and the two e100's) and whichever card is eth0 doesn't work.
Right now this doesn't cause a problem since I'm running off of eth1/eth2. It's more that this is the strangest thing I've seen in 10 years of using Linux, and I'm curious why it's doing it.
Sean
-
Sean A. Walberg -
Sean Walberg
-
Trevor Cordes