using predictable networkinterfacenames cause network issue with autoyast'ed system

I’m using autoyast to deploy a new Opensuse 13.1 X64 system.
After the autoyast installation finishes, there’s is no network active on the deployed system. i can manually enter yast → network settings and switch it to dhcp and then it’s working

but i’m puzzled. because in the xml in the networking → interface segment it clearly states DHCP

        <name>Intel Ethernet controller</name>

from what i can see in the xml networking segment.
there is a new sub-segment generated:

<net-udev config:type="list">

which might be causing the issues. could i simply remove it.? i’m not sure what it’s used for anyway.

Anyway i’m pretty confused about predictablenetworknames. since it becomes pretty unpredictable when you have multiple systems with different hardware configurations, which is our reality at my work :frowning:

It would help if you show “ifconfig -a”, “ls -l /etc/sysconfig/network”, "systemctl --full | grep network’ on a newer deployed system. This would give some starting point.

I dont think thoose commands will tell me what the "un"predictable networkname is.
Anyway. I can run biosdevname after the system is installed and get the name.

I was not aware that i now have to define a interface segment for each possible network hardware configuration we have at my workplace.
i’m sorry to say, It used to much easier with eth0, eth1 etc… in regards to autoyast.

it needs to be working both on virtual box machines, HP DC’s, Dell optiplexes, vmware player etc…
so for the INtel 82540EM (virtualbox) which is named enp0S3 (of course :-)), i add this segment to the networking part.

<name>82540EM Gigabit Network Connection</name>

and then for the DP DC 8300 which has the 82566DM-2 and predictable network name enp0S25

<name>82566DM-2 Gigabit Network Connection</name>

and so on…

if the names are so predictable. is there a magic trick to predict them without installing opensuse first and then run biosdevname

Thank You for pointing me to the other thread. Can use the perl script provided by lwfinger to get that info. :slight_smile: