SuSE 9.2 Pro changing eth0 to eth1
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? Jason Joines =================================
On Thu, 23 Dec 2004, 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?
Short version: you can't rely on the order in which the kernel (or hotplug!) recognizes and initializes the cards, therefore you cannot rely on which is eth0 and which is eth1. This has been true since the very earliest versions of the kernel (although the interface recognition has been observably static, that is purely accidental!). Thus, SuSE 9.2 and others use the MAC address to uniquely identify interfaces (yes, yes, I know MACs aren't necessarily unique either, they are "unique enough"). I suggest you look at doing something like this: mac=$(/sbin/ifconfig "$iface" | sed -n -e '/^.*HWaddr \([:[:xdigit:]]*\).*/{s//\1/;y/ABCDEF/abcdef/;p;q;}') WHich is taken verbatim from get-mac-address.sh on my Debian box. Note my MUA broke the long line, there is a space after HWaddr. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
On Thursday, December 23, 2004 02:10 pm, Jon Nelson wrote:
On Thu, 23 Dec 2004, 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?
Short version: you can't rely on the order in which the kernel (or hotplug!) recognizes and initializes the cards, therefore you cannot rely on which is eth0 and which is eth1. This has been true since the very earliest versions of the kernel (although the interface recognition has been observably static, that is purely accidental!).
Thus, SuSE 9.2 and others use the MAC address to uniquely identify interfaces (yes, yes, I know MACs aren't necessarily unique either, they are "unique enough").
I suggest you look at doing something like this: mac=$(/sbin/ifconfig "$iface" | sed -n -e '/^.*HWaddr \([:[:xdigit:]]*\).*/{s//\1/;y/ABCDEF/abcdef/;p;q;}')
WHich is taken verbatim from get-mac-address.sh on my Debian box. Note my MUA broke the long line, there is a space after HWaddr.
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point. -- _______________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business." 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.RNoME.com
L. Mark Stone wrote:
On Thursday, December 23, 2004 02:10 pm, Jon Nelson wrote:
On Thu, 23 Dec 2004, 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? Short version: you can't rely on the order in which the kernel (or hotplug!) recognizes and initializes the cards, therefore you cannot rely on which is eth0 and which is eth1. This has been true since the very earliest versions of the kernel (although the interface recognition has been observably static, that is purely accidental!).
Thus, SuSE 9.2 and others use the MAC address to uniquely identify interfaces (yes, yes, I know MACs aren't necessarily unique either, they are "unique enough").
I suggest you look at doing something like this: mac=$(/sbin/ifconfig "$iface" | sed -n -e '/^.*HWaddr \([:[:xdigit:]]*\).*/{s//\1/;y/ABCDEF/abcdef/;p;q;}')
WHich is taken verbatim from get-mac-address.sh on my Debian box. Note my MUA broke the long line, there is a space after HWaddr.
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point.
Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0" Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names. Jason ===========
On Thu, 23 Dec 2004, Jason Joines wrote:
L. Mark Stone wrote:
Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with
KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0" Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names.
Well, I learn something every day, and this is something kinda useful. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
On Thursday, December 23, 2004 03:50 pm, Jason Joines wrote:
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point.
Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with
KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0" Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names.
Jason, That's great news. I gave a presentation on udev a few months ago at the local LUG; although I used multiple USB printers as the example case, your problem was a good candidate for udev rules as well. Bonus points for no reboot, too! But, you probably should reboot the box to test at some point, don't you think? With best regards, Mark -- _______________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business." 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.RNoME.com
L. Mark Stone wrote:
On Thursday, December 23, 2004 03:50 pm, Jason Joines wrote:
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point. Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with
KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0"
Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names.
Jason,
That's great news. I gave a presentation on udev a few months ago at the local LUG; although I used multiple USB printers as the example case, your problem was a good candidate for udev rules as well.
Bonus points for no reboot, too! But, you probably should reboot the box to test at some point, don't you think?
With best regards, Mark
I rebooted to test and it failed. The NIC's went back to wrong names. Then I added another rule for the other NIC and rebooted again. Still have the same problem. Also, if I down network, reload the modules, and fire it back up, then the NIC I want comes up with eth1 but eth0 doesn't come up at all. Jason ===========
Jason Joines wrote:
L. Mark Stone wrote:
On Thursday, December 23, 2004 03:50 pm, Jason Joines wrote:
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point. Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with
KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0" Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names.
Jason,
That's great news. I gave a presentation on udev a few months ago at the local LUG; although I used multiple USB printers as the example case, your problem was a good candidate for udev rules as well.
Bonus points for no reboot, too! But, you probably should reboot the box to test at some point, don't you think?
With best regards, Mark
I rebooted to test and it failed. The NIC's went back to wrong names. Then I added another rule for the other NIC and rebooted again. Still have the same problem. Also, if I down network, reload the modules, and fire it back up, then the NIC I want comes up with eth1 but eth0 doesn't come up at all.
Jason ===========
Spoke too soon about eth0 not coming up. I had just mistyped when reloading e100. When I got both modules loaded the udev rules worked as expected. Also, it doesn't matter which I load first. However, it's still not working at boot. Jason ===========
On Tuesday January 4, 2005 10:36 am, Jason Joines wrote:
Jason Joines wrote:
L. Mark Stone wrote:
On Thursday, December 23, 2004 03:50 pm, Jason Joines wrote:
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point.
Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with
KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0" Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names.
Jason,
That's great news. I gave a presentation on udev a few months ago at the local LUG; although I used multiple USB printers as the example case, your problem was a good candidate for udev rules as well.
Bonus points for no reboot, too! But, you probably should reboot the box to test at some point, don't you think?
With best regards, Mark
I rebooted to test and it failed. The NIC's went back to wrong names. Then I added another rule for the other NIC and rebooted again. Still have the same problem. Also, if I down network, reload the modules, and fire it back up, then the NIC I want comes up with eth1 but eth0 doesn't come up at all.
Jason ===========
Spoke too soon about eth0 not coming up. I had just mistyped when reloading e100. When I got both modules loaded the udev rules worked as expected. Also, it doesn't matter which I load first. However, it's still not working at boot.
Jason ===========
I wonder if you can get this covered under SuSE's installation support? -- _______________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business." 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.RNoME.com
L. Mark Stone wrote:
On Tuesday January 4, 2005 10:36 am, Jason Joines wrote:
Jason Joines wrote:
L. Mark Stone wrote:
On Thursday, December 23, 2004 03:50 pm, Jason Joines wrote:
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point. Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with
KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0" Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names. Jason,
That's great news. I gave a presentation on udev a few months ago at the local LUG; although I used multiple USB printers as the example case, your problem was a good candidate for udev rules as well.
Bonus points for no reboot, too! But, you probably should reboot the box to test at some point, don't you think?
With best regards, Mark I rebooted to test and it failed. The NIC's went back to wrong names. Then I added another rule for the other NIC and rebooted again. Still have the same problem. Also, if I down network, reload the modules, and fire it back up, then the NIC I want comes up with eth1 but eth0 doesn't come up at all.
Jason =========== Spoke too soon about eth0 not coming up. I had just mistyped when reloading e100. When I got both modules loaded the udev rules worked as expected. Also, it doesn't matter which I load first. However, it's still not working at boot.
Jason ===========
I wonder if you can get this covered under SuSE's installation support?
I emailed the author of /usr/share/doc/packages/sysconfig/README and here's what he said. Apparently the best you can do is have static names that don't start with eth
Christian Zoz wrote:
On Tue, Jan 04, Jason Joines wrote:
Christian,
Lines 107 and 108 of /usr/share/doc/packages/sysconfig/README on my SuSE 9.2 Pro box read, "always be used for the device with MAC address 00:e0:98:a0:83:c2. And inside this configuration name you may specify a persistent interface name."
What is the syntax for specifiying a "persistent interface name"? I've been unable to find it in man pages, README's, etc. There's a
PERSISTENT_NAME=
Don't use eth* or other names used by the kernel.
Jason ===========
On Monday, January 10, 2005 02:53 pm, Jason Joines wrote: <snip>
I emailed the author of /usr/share/doc/packages/sysconfig/README and here's what he said. Apparently the best you can do is have static names that don't start with eth
Christian Zoz wrote:
On Tue, Jan 04, Jason Joines wrote:
Christian,
Lines 107 and 108 of /usr/share/doc/packages/sysconfig/README on my SuSE 9.2 Pro box read, "always be used for the device with MAC address 00:e0:98:a0:83:c2. And inside this configuration name you may specify a persistent interface name."
What is the syntax for specifiying a "persistent interface name"? I've been unable to find it in man pages, README's, etc. There's a
PERSISTENT_NAME=
Don't use eth* or other names used by the kernel.
Jason ===========
Of course I remember that now; sorry my brain froze and I did not recall this earlier--I know it would have saved you a lot of time. -- ___________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine LLC "We manage your network so you can manage your business." 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com
Op donderdag 23 december 2004 21:50, schreef Jason Joines:
Thanks for the tip. Similar information is in the SuSE 9.2 Pro Admin Guide, I just didn't know I needed to look for udev. Using that, your link and http://www.reactivated.net/udevrules.php I got this straightened out. The man page for udev said files ending in .rules were loaded from /etc/udev/rules.d in alphabetical order. There was only one file ther, 50-udev.rules, so I created 49-udev.rules with
KERNEL="eth*", SYSFS{address}="00:06:5b:05:f2:8f", NAME="eth0" Then I shutdown networking with 'rcnetwork stop', unloaded the modules with 'rmmod e100 tg3', loaded 'em back up, started networking back up, and the NICs had the desired names.
Could you be using this too: file:/usr/share/doc/manual/suselinux-adminguide_en/html/ch22s04.html 22.4.6. Hotplug and PCMCIA Hotplug devices are no longer treated in a special way, because all devices are initialized by hotplug. Nevertheless, physical hotplug is characterized by some special aspects. When the system is booted, built-in devices are always initialized in the same order and receive the same interface names from the kernel. Interface names are assigned dynamically by the kernel. As soon as an interface is registered, it is assigned the next free name. Because hotplug devices can be inserted at random, they do not always receive the same interface names. Nevertheless, they are assigned the same configurations, because the configurations do not depend on the interface names. If you prefer persistent interface names, enter PERSISTENT_NAME=name in the respective interface configuration file (/etc/sysconfig/network/ifcfg-*). This setting will be adopted the next time the card is initialized (inserted). -- Richard Bos Without a home the journey is endless
On Thu, 2004-12-23 at 14:35 -0500, L. Mark Stone wrote:
On Thursday, December 23, 2004 02:10 pm, Jon Nelson wrote:
On Thu, 23 Dec 2004, Jason Joines wrote:
What does "install eth0 /bin/true" do and how can I specify which NIC gets eth0 and which gets eth1?
Short version: you can't rely on the order in which the kernel (or hotplug!) recognizes and initializes the cards, therefore you cannot rely on which is eth0 and which is eth1. This has been true since the very earliest versions of the kernel (although the interface recognition has been observably static, that is purely accidental!).
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point.
Further Googling reveals: http://article.gmane.org/gmane.linux.gentoo.user/75158 The important bit seems to be to get the modules in place before the hotplug service starts up. I found this, which says the whole modprobe business is deprecated in favor of sysfs and udev. It seems to get right up to the point of showing how to do what you want to do, then stops. http://216.239.39.104/translate_c? hl=en&sl=de&u=http://portal.suse.com/sdb/de/2004/05/91_sysconfig.html&prev=/search%3Fq%3Dsuse%2Budev%2Beth0%2Beth1%26hl%3Den%26lr%3D%26sa%3DG So close... yet so far... dk
David Krider wrote:
On Thu, 2004-12-23 at 14:35 -0500, L. Mark Stone wrote:
On Thursday, December 23, 2004 02:10 pm, Jon Nelson wrote:
On Thu, 23 Dec 2004, Jason Joines wrote:
What does "install eth0 /bin/true" do and how can I specify which NIC gets eth0 and which gets eth1? Short version: you can't rely on the order in which the kernel (or hotplug!) recognizes and initializes the cards, therefore you cannot rely on which is eth0 and which is eth1. This has been true since the very earliest versions of the kernel (although the interface recognition has been observably static, that is purely accidental!).
You might also want to try setting up a few rules in /etc/udev/rules.d/udev.rules to name the devices. See http://www-uxsup.csx.cam.ac.uk/suse/adminguide-sles9/ch15.html as a starting point.
Further Googling reveals:
http://article.gmane.org/gmane.linux.gentoo.user/75158
The important bit seems to be to get the modules in place before the hotplug service starts up.
I found this, which says the whole modprobe business is deprecated in favor of sysfs and udev. It seems to get right up to the point of showing how to do what you want to do, then stops.
http://216.239.39.104/translate_c? hl=en&sl=de&u=http://portal.suse.com/sdb/de/2004/05/91_sysconfig.html&prev=/search%3Fq%3Dsuse%2Budev%2Beth0%2Beth1%26hl%3Den%26lr%3D%26sa%3DG
So close... yet so far...
dk
The udev rules solution seems to be working fine. Jason ===========
On Thu, 2004-12-23 at 11:42 -0600, Jason Joines wrote:
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?
Jason Joines
I got lucky. Since updating my firewall from 8.2 to 9.2, the interfaces just lined up like I wanted. Have you tried commenting those "install eth? /bin/true" lines out of modprobe.conf, hopefully letting your "alias ..." lines in modprobe.conf.local do their magic? Regards, dk
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.
participants (6)
-
David Krider -
James Knott -
Jason Joines -
Jon Nelson -
L. Mark Stone -
Richard Bos