Hello, Thanks for your reply. However during installation of the system i can't do what you describe. I think before installation i'm just going to disable all but 1 network card in the bios, do the installation using the working interface and afterward re-enab le all cards in the bios again. This at least insures me that the card i pick to boot from is recognized by linux as eth0. BTW, the order of the interfaces depends on the order in which the modules are loaded (assuming you have cards with different drivers) and then on the mac address. Rgds, Johan ----- Original Message ---- From: Michael Kershaw <mike.kershaw@gmail.com> To: aquajtk-slesay0605@yahoo.com Cc: suse-autoinstall@suse.com Sent: Monday, June 12, 2006 5:48:40 PM Subject: Re: [suse-autoinstall] Order of network interfaces? Hello there! The order of the network interfaces pretty much comes up in chronological order from the MAC addresses of the interfaces in the machine. A way to bind them in the order that you want them to come up in, is using the "nameif" utility. Atleast it's the way that I use to do this task. I edit the network rc-script. Open it up in vi and go to the end of the section regarding "NETWORK_RUNFILE". The closing "fi" should be at line 117. Here's what my entries look like: # we down the interfaces first /sbin/ifdown eth0 /sbin/ifdown eth1 /sbin/ifdown eth2 /sbin/ifdown eth3 # then we name them to something else outside of the ethX realm /sbin/nameif foo0 00:14:5e:0b:65:82 /sbin/nameif foo1 00:14:5e:0b:65:83 /sbin/nameif foo2 00:10:18:17:0C:D2 /sbin/nameif foo3 00:10:18:17:0C:D3 # here we bind the MAC addresses to the order of the interfaces that you want /sbin/nameif eth0 00:14:5e:0b:65:82 /sbin/nameif eth1 00:14:5e:0b:65:83 /sbin/nameif eth2 00:10:18:17:0C:D2 /sbin/nameif eth3 00:10:18:17:0C:D3 # and here we up the interface /sbin/ifup eth0 /sbin/ifup eth1 /sbin/ifup eth2 /sbin/ifup eth3 I hope this helps you out a little. Good Luck, Mike On 6/12/06, Johan Kielbaey <aquajtk-slesay0605@yahoo.com> wrote:
Hello,
I'm using a http repository with tftp and dhcp. The environment i'm working in has meanly IBM servers, but from different models (x346, x306m, x366, ...). For each model i need to investigate which interface used by pxe maps to which ethX interface in linux. This gets even worse if with a new delivery there is another type of network card in the PCI slot.
How are you handling different hardwaremodels? Is there a way to make sure that the 1st onboard interface also maps to eth0?
This is my pxe-config file :
#default label linux kernel linux-9sp3 append initrd=initrd-9sp3 ramdisk_size=65536 insmod=bcm5700 install=http://192.168.71.1/rp/x86/SLES9SP3 instmode=http bootpwait=10 dhcptimeout=120 usedhcp=1 textmode=1 autoyast=http://192.168.71.1/cf/sltr001/cf
Thanks,
Johan
Mvg - Rgds
Johan <johankielbaey@yahoo.com>
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com