<font color="#3333ff"><font face="verdana,sans-serif">Open BSD does not follow most UNIX convention while scanning for hardware. It not only scans the bus, but it also looks at the type of hardware and connection to give it a name/number designation.<br>
<br>Linux on the other hand, more like Solaris, scans the PCI and assigns the name/number as and when it finds it.<br>So if you have 8 cards or ports, the first port(according to the kernel) is always going to be eth0, so even if you plug your network into 8th port, it wont be called eth0, but eth7. (Of course assuming that all ports have different mac address, on solaris/sparc, you can assign the same mac address to all ports on the SAME card.)<br>
<br>If you are in doubt as to what the network name/number is assigned, just check 'dmesg'. Use lspci to find all your network devices.<br><br>@ work, many years ago, when we built RHEL 2 and 3 servers, we always cabled all the servers(dell) the same way(4 ports of ethernet, of which 2 will be used). None of them had an issue with different network names. At one point we built 22 servers in 24 hours.<br>
<br>Summary: What you see on Linux is normal behavior for Linux, HP-UX, AIX, Irix and Solaris.<br>-GGR <br clear="all"></font></font><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><br>--</span><br style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">
<span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Rajiv G Gunja</span><br style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Blog: <a href="http://ossrocks.blogspot.com" target="_blank">http://ossrocks.blogspot.com</a></span><br>
<br><br><div class="gmail_quote">On Wed, Mar 23, 2011 at 12:41, <span dir="ltr"><<a href="mailto:jecottrell3@comcast.net">jecottrell3@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This is totally unrelated, but it makes a good story.<br>
<br>
Last year I was building servers in a rack and found out that altho the NICs are numbered 0 thru 3 on the chassis, Linux calls NIC 0 "eth2".<br>
<br>
The only way i found this out was by ifconfig'ing each interfact up individually until one worked. I'm not sure what the rest of the mapping are.<br>
<br>
The reason for this is most likely that there are actually two different type of ethernets, each with two ports, and the devices are probed in a differrent order than SUn (it's a SunFire X4200) would do it.<br>
<br>
JIM<br>
<div><div></div><div class="h5"><br>
----- Original Message -----<br>
From: "Jim Bauer" <<a href="mailto:jfbauer@comcast.net">jfbauer@comcast.net</a>><br>
To: <a href="mailto:calug@unknownlamer.org">calug@unknownlamer.org</a><br>
Sent: Wednesday, March 23, 2011 6:58:50 AM<br>
Subject: Re: [CALUG] Random Network Interfaces<br>
<br>
On 03/22/2011 11:32 PM, Randal T. Rioux wrote:<br>
> Greetings.<br>
><br>
> I haven't used Linux as a router/firewall in 15 years. Usually use<br>
> OpenBSD or dedicated appliances. I wanted to give RHEL6 a shot and<br>
> experienced some oddities.<br>
><br>
> I've also tested this with Slackware 13.1 for the record.<br>
><br>
> I have 8 NICs on an IBM x345. With OpenBSD, I can reboot and switch<br>
> cables and networks and the NIC devices are always named the same.<br>
><br>
> Doing the same with RHEL and Slackware keeps<br>
> incrementing/adding/removing eth's each time (messing up IP assignments<br>
> and causing general mayhem), i.e. eth0 because eth3, eth5 is gone, etc.<br>
><br>
> Is this a feature? Can somebody explain this to me? My Web search foo<br>
> must be weak this evening.<br>
><br>
<br>
This might be the same thing I noticed a while back with ubuntu when I<br>
replaced some ancient network cards with something more modern and the<br>
eth numbers all changed (except for the one card I left in place). I<br>
tracked it to udev. It remembers the MAC addresses and if eth0 had<br>
01:02:03:04:05:06 then eth0 will always have that mac address. So it<br>
you replace that card with another, the new card will get the next<br>
available ethN. And if you ever put back that old card, it'll reappear<br>
as eth0. I believe /etc/udev/rules.d/70-persistent-net.rules is where<br>
that is recorded.<br>
<br>
<br>
_______________________________________________<br>
CALUG mailing list<br>
<a href="mailto:CALUG@unknownlamer.org">CALUG@unknownlamer.org</a><br>
<a href="http://lists.unknownlamer.org/listinfo/calug" target="_blank">http://lists.unknownlamer.org/listinfo/calug</a><br>
<br>
_______________________________________________<br>
CALUG mailing list<br>
<a href="mailto:CALUG@unknownlamer.org">CALUG@unknownlamer.org</a><br>
<a href="http://lists.unknownlamer.org/listinfo/calug" target="_blank">http://lists.unknownlamer.org/listinfo/calug</a><br>
</div></div></blockquote></div><br>