Eric Hines wrote:
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?
Either I'm missing something or you're missing something. Those files are tied directly to a NIC, with the corresponding MAC address. They don't work with any other. Now eth0, eth1 etc., may wander around, but why is that an issue? Servers talk to IP addresses, not NICs. It's up to the IP stack to figure out which NIC to talk to. You shouldn't have any need to worry about whether a NIC is eth0 or not.