<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16700"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI">I like your analogy David..." rock is too small to be turned around now" I think you put it in the right context. It is always a good idea to check on dmesg upon boot and make sure those modules are loaded as David mentioned. Try to start from the beginning to troubleshoot the problem. Tow cents.<BR><BR>>>> David Sommerseth <dazo@users.sourceforge.net> 1/10/2011 3:05 AM >>><BR>On 10/01/11 05:41, Rudi Ahlers wrote:<BR>> On Sun, Jan 9, 2011 at 11:13 PM, Robert Spangler<BR>> <mlists@zoominternet.net> wrote:<BR>>> On Sunday 09 January 2011 13:33, Rudi Ahlers wrote:<BR>>><BR>>>> Our intranet's WAN interface just stopped working yesterday, and I<BR>>>> can't figure it out.<BR>>><BR>>> Look in /etc/sysconfig/network-scripts. There you should see ifcfg-eth# If<BR>>> ifcfg-eth0 isn't there copy ifcfg-eth1 to ifccfg-eth0 and then configure<BR>>> ifcfg-eth0 to the information needed for your WAN link.<BR>>><BR>> <BR>> The device file exists, but it's like asif the network card itself<BR>> doesn't exist.<BR><BR>My immediate hunch is ... and I'm sorry to say it ... but your NIC is<BR>often referred to as Realcrap NICs - unfortunately that's not without a<BR>reason.<BR><BR>However, check what lspci says. If you don't see your NIC there, it is<BR>most likely a hardware issue (or caused by BIOS changes). If you see<BR>it, then look closely in dmesg for anything related to loading the<BR>kernel module for this NIC. See if that spits out any error messages.<BR>You may also try to reload your NICs kernel module (modprobe -r <module><BR>&& modprobe <module>).<BR><BR>Another thing is to figure out what you did before it stopped working.<BR>If you want to say "I did nothing" and that means you rebooted your box,<BR>upgraded packages or other things which might sound safe and innocent,<BR>it might just as well be connected.<BR><BR>The only times I've experienced issues and where I really did nothing,<BR>it was related to physical hardware issues. But those times where I did<BR>"nothing" (rebooting, upgrading, innocent configuration changes) and got<BR>troubles ... it was always connected to that I did the "nothing" thing.<BR>Sometimes even disabling "useless features" in BIOS turned out to<BR>disable quite a useful feature after all.<BR><BR>So no rock is too small to be turned around now. Go carefully through<BR>all your changes you did before it stopped working.<BR><BR><BR>kind regards,<BR><BR>David Sommerseth<BR><BR>_______________________________________________<BR>CentOS mailing list<BR>CentOS@centos.org<BR><A href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</A><BR></BODY></HTML>