Subject: Re: [SLE] SUSE 9.3 Pro and 3 NICs

At 12/25/05 07:51, James Knott wrote:

...

Eric Hines wrote:

...

At 12/24/05 18:53, James Knott wrote:

...

Eric Hines wrote: <snip>

Alternatively, how do I use YaST to do this? I've been in YaST|Network Devices|Network Card|<NIC>|Edit and edited the IP address for each. I can't find any place to pin a NIC to a particular ethx, though. And both the addresses and the ethx change on each boot--e.g., eth0 will have on NIC (by MAC address) and one IP address after one bootup, and after another bootup it'll have a different NIC and a different IP address (and both will be completely different--it won't simply be a NIC/IP address pairing from another ethx on the earlier bootup).

I'm not sure what you're getting at here. If you use the ifcfg files, you'll always configure the correct NIC. If you need to refer to the NICs in a script, you use the full name.

<snip>

One of the problems I have--and I'll try editing the files directly, to guarantee that I'm configuring the correct NIC with the correct information--is that it doesn't seem to make any difference how I configure each NIC--or whether I configure them at all--on one boot up, eth0, say, will have NIC1, with IP address 2, attached to it, and on a subsequent bootup, eth0 will have NIC2, with IP address 3, attached to it, even though I have done nothing at--just boot up, run ifconfig -a to see what's where, then shut down. Similarly, there's no pairing between NIC and IP address--these change on their own, also: NIC3 with IP address 1 on one bootup will have, on the next bootup, IP address 3 attached.

Also, even editing the files directly, I could see no way to pin a NIC to a specific eth. How do I do that?

Thanks

Eric Hines

Reading the man page on ifstatus, and probably with a large dose of a little knowledge is a dangerous thing, I'm reminded of further events that I should have reported at the outset. When I installed the Netgear NIC, SUSE found it right off and offered to let me configure it, which I did, via the YaST that SUSE presented. However, on each of the next several (5-6) cold boot ups, SUSE found the Netgear all over again and presented YAST for me to configure the Netgear. As I entered the YAST module, I saw that the Netgear was already configured, from my earlier setup. SUSE has stopped newly finding the Netgear lately, and it shows up (as it did even when it was being "newly found," and I was declining to configure it yet again) in ifconfig -a as though it's working properly. It's like the Netgear never got properly registered in the kernel. How can I check this, and how can I register it, if that needs to be done? Additionally, this is what I may be beginning to understand: eth0 is an interface 00:11:11:...:A2 is a device (i.e., a NIC) ifcfg-eth-id... with IP addresses, and so on, is a configuration. I don't care if NIC/ethx pairing remains constant, all I care about is whether NIC/IP address remains constant. Is this right? All I have to do is solve the wandering NIC/IP address pairing problem? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell