On 10/01/11 05:41, Rudi Ahlers wrote:
> On Sun, Jan 9, 2011 at 11:13 PM, Robert Spangler
> <mlists@xxxxxxxxxxxxxxxx> wrote:
>> On Sunday 09 January 2011 13:33, Rudi Ahlers wrote:
>>
>>> Our intranet's WAN interface just stopped working yesterday, and I
>>> can't figure it out.
>>
>> Look in /etc/sysconfig/network-scripts. There you should see ifcfg-eth# If
>> ifcfg-eth0 isn't there copy ifcfg-eth1 to ifccfg-eth0 and then configure
>> ifcfg-eth0 to the information needed for your WAN link.
>>
>
> The device file exists, but it's like asif the network card itself
> doesn't exist.
My immediate hunch is ... and I'm sorry to say it ... but your NIC is
often referred to as Realcrap NICs - unfortunately that's not without a
reason.
However, check what lspci says. If you don't see your NIC there, it is
most likely a hardware issue (or caused by BIOS changes). If you see
it, then look closely in dmesg for anything related to loading the
kernel module for this NIC. See if that spits out any error messages.
You may also try to reload your NICs kernel module (modprobe -r <module>
&& modprobe <module>).
Another thing is to figure out what you did before it stopped working.
If you want to say "I did nothing" and that means you rebooted your box,
upgraded packages or other things which might sound safe and innocent,
it might just as well be connected.
The only times I've experienced issues and where I really did nothing,
it was related to physical hardware issues. But those times where I did
"nothing" (rebooting, upgrading, innocent configuration changes) and got
troubles ... it was always connected to that I did the "nothing" thing.
Sometimes even disabling "useless features" in BIOS turned out to
disable quite a useful feature after all.
So no rock is too small to be turned around now. Go carefully through
all your changes you did before it stopped working.
kind regards,
David Sommerseth
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
