...

I have a box with 2 NICs in it. SuSE 9.2 Pro.

...

One Realtek that starts up as eth0, and a Broadcom that starts up as eth1. So far, so good.

...

But suddenly after a reboot, they've changed places? The Realtek is then eth1 and the Broadcom is eth0.

...

A couple of reboots later, they've changed places again! How can I control this? I need static naming since I have apps that depends on the correct name/network.

Manually activate them in the right order .. the first one to get actovated becomes eth0, the second one becomes eth1 &c

That's no solution. The box need to be able to reboot itself to a full running status without manual intervention. Anders.

...

I have a box with 2 NICs in it. SuSE 9.2 Pro.

One Realtek that starts up as eth0, and a Broadcom that starts up as eth1. So far, so good.

But suddenly after a reboot, they've changed places? The Realtek is then eth1 and the Broadcom is eth0.

A couple of reboots later, they've changed places again!  How can I control this? I need static naming since I have apps that depends on the correct name/network.

look for PERSISTANT_NAME in the suse docu.

I found PERSISTENT_NAME, and as I understand, I should add a line in the /etc/sysconfig/network/ifcfg-eth-id-...... files to control the device name. So, of course I tried, but the names after reboot was just the opposite of what I had entered. Anders.

...

...

...

I have a box with 2 NICs in it. SuSE 9.2 Pro.

One Realtek that starts up as eth0, and a Broadcom that starts up as eth1. So far, so good.

But suddenly after a reboot, they've changed places? The Realtek is

On Mon, 2005-03-14 at 10:53, Anders Norrbring wrote: then

...

...

...

eth1 and the Broadcom is eth0.

A couple of reboots later, they've changed places again! How can I control this? I need static naming since I have apps that depends on the correct name/network.

look for PERSISTANT_NAME in the suse docu.

I found PERSISTENT_NAME, and as I understand, I should add a line in the /etc/sysconfig/network/ifcfg-eth-id-...... files to control the device name. So, of course I tried, but the names after reboot was just the opposite of what I had entered.

So then you went back into the file and switched them to get them correct? And now they are the way you want them?

Nope, sorry that I didn't make it clear. The config that has PERSISTENT_NAME='eth0' is labelled eth1 and vice versa. Alas, just the opposite of what I want. I've now rebooted a number of times, and every now and then the labelling changes (to what I want), and then changes back again. Seems like there's no logic at all in this.. Anders.

On Monday 14 March 2005 18:40, Jeffrey L. Taylor wrote:

Quoting Anders Norrbring :

...

Nope, sorry that I didn't make it clear. The config that has PERSISTENT_NAME='eth0' is labelled eth1 and vice versa.

Alas, just the opposite of what I want.

RTFM - from section 22.3:

* Persistent interface names can be assigned to all interfaces whose configurations do not bear the interface names. This can be done by means of entries PERSISTENT_NAME=<pname> names in an interface configuration (ifcfg-*). However, the persistent name pname should not be the same as the name that would automatically be assigned by the kernel. Therefore, eth*, tr*, wlan*, qeth*, iucv*, and so on are not permitted. Instead, use net* or descriptive names like external, internal, or dmz. A persistent name can only be assigned to an interface immediately after its registration, which means that the driver of the network card must be reloaded or hwup <device description> must be executed. The command rcnetwork restart is not sufficient for this purpose.

You cannot use eth0 and eth1 for persistent names ;P

Try net0 and net1.

Jeffrey

Not my scene, but thats very sad, I have never experienced this. to put it bluntly if it happened to me I would tear the YAST config apart and rebuild it with init scripts. However there must be a logical reason for it swopping, such as the time the driver takes to load or the sequence in which the cards are detected, as some one mentioned before you should be able to control it with /etc/modules.conf Thats where I would start, use google for solutions and try a few. then if that fails I would "can" YAST and do my own scripts to start it properly named the way I want it -- ON BOOT. Suse is still linux, you can still do it anyway you like :) rgrds and Good Luck Chad

Op maandag 14 maart 2005 16:53, schreef Anders Norrbring:

...

I found PERSISTENT_NAME, and as I understand, I should add a line in the /etc/sysconfig/network/ifcfg-eth-id-...... files to control the device name. So, of course I tried, but the names after reboot was just the opposite of what I had entered.

Anders.

Related to this; if one configures the 2 nics with yast , the latter insist (in my case at least) on having a hostname, name server, domain, etc for both nics (this is with 2 fixed ip addresses).

Isn't that strange? Should the name for the nics not be different for each one. For eth0 e.g. linux and for the other nic (eth1) e.g.; linux-eth1?

And wouldn't it be sufficient if one of the nics carried the name server(s), search domain and domain instead of having both cards carry that information?

Richard, The NIC's could be on totally different networks.. :) Like in my case. That's why it's so important that eth0 stays as eth0 since it's called on from softwares. Anders.