Jason Joines wrote:
I'm trying to get SuSE 9.2 Pro installed on a machine with two NIC's. It was previously running 9.1 and whichever NIC I configured first got eth0. That doesn't work with 9.2. I'm not sure how it's choosing which one gets eth0 but it seems to always picke the one that should be eth1.
I tried disabling the NIC I want to be eth1 in the BIOS and then re-installing. After the install, the one I wanted to have eth0 did have it. Then I re-enabled the other NIC and when the box came up it had swapped eth0 and eth1 again.
Seems modprobe.conf has replaced modules.conf and says to make changes in modprobe.conf.local. I tried adding "alias eth0 e100" (the NIC that should be eth0 is an Intel using e100 and the one that should be eth1 is a BroadCom using something else) as the only line in modprobe.conf.local but that did not work. The first couple of lines in modprobe.conf are "install eth0 /bin/true" and "install eth1 /bin/true". I've read the modprobe.conf man page but still have not idea what those lines are doing and there are no "alias eth0 ..." or "alias eth1 ..." lines anywhere.
What does "install eth0 /bin/true" do and how can I specify which NIC gets eth0 and which gets eth1?
If you use eth0 or eth1, you may have this problem. However, if you look in /etc/sysconfig/network, you'll see something like ifcfg-eth-id-00:05:5d:fe:fc:e4, which included the mac address. If you use that type of designation, you can specify the exact piece of hardware to use. So, instead of, for example ifup eth0, you'd use ifup ifcfg-eth-id-00:05:5d:fe:fc:e4.