My NIC's name changed for eth0 to eth_s0_0

English Network/Internet
1

I moved my hard drive with openSUSE 12.1 on it, over to a new computer (with a faster CPU). So on first boot the name of the NIC in openSUSE 12.1 changed from eth0 to eth_s0_0. This has mucked up my VMs which expect eth0 to be available. Now the VMs won’t boot.

I’d like to restore the old name eth0 to my network interface. How would I do that?

Thanks

swerdna

2

On 12/13/2011 05:26 PM, swerdna wrote:
>
> I moved my hard drive with openSUSE 12.1 on it, over to a new computer
> (with a faster CPU). So on first boot the name of the NIC in openSUSE
> 12.1 changed from eth0 to eth_s0_0. This has mucked up my VMs which
> expect eth0 to be available. Now the VMs won’t boot.
>
> I’d like to restore the old name eth0 to my network interface. How
> would I do that?

Look for rules in /etc/udev/rules.d that are left over from the old version. If
none are there, you may need to add one.

3

This is normal. Everytime you add or replace a nic - whether it’s on board or not - the interface name gets incremented because the older udev rule - based on the MAC address - doesn’t get deleted. If you don’t have the older nic anymore, you can safely write the MAC address of the new one in the line ending with NAME=“eth0” in the file /etc/udev/rules.d/70-persistent-net.rules.

What’s troubles me in that normally, it should have been called eth1, eth2, etc. I wonder if you’re not talking about the connection name … which might be different from the interface name. Probably both have changed. Anyway, you should first run ifconfig -a to see the interface name and its MAC address.

Notice that fedora since version 15 uses a new approach, called Features/ConsistentNetworkDeviceNaming - FedoraProject - which is not much better, IMO. I’ve seen consistent names changing too.

4

Thanks guys – that advice worked. I edited the line for the card in the file you pointed to, made sure the mac address matched and the name I changed to eth0. Then played around in Yast netwok settings a bit, then rebooted and it came back as eth0. [and now my VMs work too].