rhel4 detects NICs in reverse on a 2950

[J. Epperson]

On Tue, September 5, 2006 20:21, G-man wrote:
>
> Anyone else having the problem of the network cards being detected in
> reverse on a 2950? Took a little while to figure out when kickstarting
> rhel4u4 via pxe. eth0 is actally the NIC marked "2" on the back of the
> computer. I would expect eth0 to be the one marked "1".
>
> Any ideas how I can fix this? I can set HWADDR in ifcfg-eth0 post
> install, but that is more of a bandaid  fix.
>
On Tue, August 1, 2006 18:10, Matt Domsch wrote:
> I've released version 0.3 of my name_eths program, adding support for
> SLES10 in addition to the support for Red Hat and Fedora
> distributions.
>
> This program uses BIOS information to assign the system's embedded
> NICs the lowest ethX numbers, and assigns NICs in add-in slots to
> higher ethX numbers.  This avoids confusion caused by the BIOS and
> printed docs specifying the embedded devices as NIC1 and NIC2, when
> Linux then finds them in the reverse order eth1 and eth0.  Using
> name_eths, NIC1 and NIC2 get assigned to eth0 and eth1 as would be
> expected.
>
> http://linux.dell.com/files/name_eths/name_eths-0.3.tar.gz
> http://linux.dell.com/files/name_eths/name_eths-0.3.tar.gz.sign
>
> Thanks,
> Matt
>
> P.S.
> If using Red Hat's anaconda installer and you have only one NIC
> with a cable plugged in, use 'ksdevice=link', then use name_eths after
> installation is complete.
>
> If using Red Hat's anaconda installer and PXELinux, the PXELinux
> option IPAPPEND can be used to have anaconda use the same NIC that
> is used for PXE booting.  See the syslinux documentation for more
> information.
>
> If all else fails, use ksdevice=macaddr, where macaddr is the MAC
> address of the NIC you want to use for the install.  See the anaconda
> docs or sourcecode for more details.