ens network interface (ens32) instead of eth0 - what's wrong?

Hi,

I checked google for answer, but didn’t find any. Here is my problem:

Lately I installed openSUSE 13.1 on vmware (as a virtual machine). After booting machine up it turns out, that it has no eth0 interface… Instead of it, some “ens32” appeared. In yast i can’t just change the name of interface. Rebooting, changing /etc/sysconfig/network/ifcfg-ens32 to eth0 , etc didn’t help.

How to change this anoying ens32 to eth0 ? Can someone explain, why i don’t have eth0 (after fresh installation of openSUSE) ?

Thanks!

Because the naming of NIC devices changed.
See: http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

Thanks!

So, it’s a feature, not a bug…
Anyway, on the bottom of the article, there is a way of how to disable it, and return to “ethX” thing.

Cheers!

Yes, but it is not allways wise to go against a new way of doing things.
In general I advise either to simply accept it, or use the escape to get things running and then make a plan on how you can adopt befor further developments get you in a corner (at a moment you can not afford it).

On 2014-06-09 16:06, maciejkola wrote:

> So, it’s a feature, not a bug…
> Anyway, on the bottom of the article, there is a way of how to disable
> it, and return to “ethX” thing.

If you are using YaST for network configuration, then in the network
configuration module, choose “edit” on the appropriate card, then on the
hardware tab choose change device name to whatever you want.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

You are right - I didn’t notice it earlier. Here is the screenshot for those having difficult in finding it:

http://postimg.org/image/j5tvbuxh1/

http://postimg.org/image/j5tvbuxh1/