<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" bgColor=#ffffff>
<DIV>Tommy,</DIV>
<DIV>I think your scenario only pertain to those of us that clone macs with different prefixes, we are assuming that rudi is using the original MAC from the actual device. Not two macs are equal unless you change the physical device parameters via mac-changer/modification. Let's hope he is not aliasing the original mac with a multi-fake mac group link to the original NIC.</DIV>
<DIV> </DIV>
<DIV>>>> Tommy E Craddock Jr <tommy@hivelocity.net> 1/10/2011 8:54 AM >>><BR></DIV>
<DIV>Hey,</DIV>
<DIV><BR></DIV>
<DIV>If it happens again, or maybe it might show in /var/log/messages, if there was a MAC address conflict in the ifcfg files. I've seen where eth0 won't come on as the MAC address set in the cfg file wasnt matching. Some times it fails with a message on an ifdown ifup, sometimes it doesn't. Now that eth2 was created and the MAC is matching it works. The pieces line up but doesn't mean that it was happened. Just an idea. </DIV>
<DIV><BR></DIV>
<DIV>Tommy C. </DIV>
<DIV><BR>On Jan 10, 2011, at 6:18 AM, Rudi Ahlers <<A href="mailto:Rudi@SoftDux.com">Rudi@SoftDux.com</A>> wrote:<BR><BR></DIV>
<DIV></DIV>
<BLOCKQUOTE type="cite">
<DIV><SPAN>On Mon, Jan 10, 2011 at 12:08 PM, Rudi Ahlers <<A href="mailto:Rudi@softdux.com">Rudi@softdux.com</A>> wrote:</SPAN><BR>
<BLOCKQUOTE type="cite"><SPAN>On Mon, Jan 10, 2011 at 11:49 AM, compdoc <<A href="mailto:compdoc@hotrodpc.com">compdoc@hotrodpc.com</A>> wrote:</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>I love realtek - the resources they use tend not to conflict with other</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>cards or hardware, they don't use much cpu time, the drivers are mature, and</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>they don't cost much. What could be better? There does seem to be at least</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>one onboard realtek chipset that can have driver issues, but I use the 8169</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>without problems.</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>But hardware does fail. And any brand of nic can fail in odd ways. I'm</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>guessing you've swapped it out?</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>Yes, the NIC might have failed, but how do I tell? lspci still shows</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>it as active.</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><FONT class=Apple-style-span color=#005001><BR></FONT></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>Bios settings can change if the on-board battery is dead and the system</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>loses power. (It can set to defaults) But bios settings rarely affect nics -</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>you're more likely to see boot problems from a change in drive boot</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>sequence.</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>I already checked, BIOS settings didn't change :)</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>I don't suppose you have a vpn on your lan? I noticed you use the</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>192.168.1.x address range, which is one of the most common ranges in the</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>world. If someone connects to your vpn from home or workplace, and if they</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>use the same range, and if theres a bridge, addresses are going to</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>conflict.</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>This is purely cause the ADSL router in the office is on the</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>192.168.1.0 subnet, so it's less hassle when it needs to be swapped</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>out to get it back up again. No VPN.</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>If you delete your ifcfg-eth0 or ifcfg-eth1 files, centos will recreate them</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>if it sees the nics at boot. But it tends to enable eth0 and disable eth1 or</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>higher. You should have backups of your originals for that reason...</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>I've already tried that, but eth0 doesn't automatically get detected.</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>I bet you wish you had a tcp/ip based kvm switch system about now...</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>Yes, I supposed I could take one from a client server, or open a</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>sealed one, but it's not really necessary. For now I put in another</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>D-Link and got the server up that way, but would prefer to use the</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>onboard one since I had to take everything out of the 1U chassis,</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN>which doesn't support more than 1 additional NIC.</SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN>_______________________________________________</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE><SPAN></SPAN><BR><SPAN>This is really weird, after I installed the 2nd D-Link card and booted</SPAN><BR><SPAN>up the server everyone could work again. But I noticed and eth2 being</SPAN><BR><SPAN>loaded as well, which could only make sense if the onboard NIC was in</SPAN><BR><SPAN>fact still working. And it was. So I took out the D-Link, deleted</SPAN><BR><SPAN>eth2, rebooted and it worked again as normal.</SPAN><BR><SPAN></SPAN><BR><SPAN>Why would this happen, or have happened in the first place? Why would</SPAN><BR><SPAN>a NIC just loose it's drivers like that?</SPAN><BR><SPAN></SPAN><BR><SPAN></SPAN><BR><SPAN>-- </SPAN><BR><SPAN>Kind Regards</SPAN><BR><SPAN>Rudi Ahlers</SPAN><BR><SPAN>SoftDux</SPAN><BR><SPAN></SPAN><BR><SPAN>Website: <A href="http://www.SoftDux.com"><A href="http://www.SoftDux.com">http://www.SoftDux.com</A></A></SPAN><BR><SPAN>Technical Blog: <A href="http://Blog.SoftDux.com"><A href="http://Blog.SoftDux.com">http://Blog.SoftDux.com</A></A></SPAN><BR><SPAN>Office: 087 805 9573</SPAN><BR><SPAN>Cell: 082 554 7532</SPAN><BR><SPAN>_______________________________________________</SPAN><BR><SPAN>CentOS mailing list</SPAN><BR><SPAN><A href="mailto:CentOS@centos.org">CentOS@centos.org</A></SPAN><BR><SPAN><A href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</A></SPAN><BR></DIV></BLOCKQUOTE></BODY></HTML>