https://bugzilla.novell.com/show_bug.cgi?id=809843 https://bugzilla.novell.com/show_bug.cgi?id=809843#c14 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |werner@suse.com --- Comment #14 from Robert Milasan <rmilasan@suse.com> 2013-03-19 08:42:16 UTC --- Well I suppose $ETHNUM you expect it to be something like eth0 or eth1 and so on, but this was the main issue with the persistent rules that it can end-up in a collision due to what the kernel says the device name is and what you wanna name the device. Could you try this: created a new file in /usr/lib/udev/rules.d/80-net-name-slot.rules and add the following: -- # do not edit this file, it will be overwritten on update ACTION=="remove", GOTO="net_name_slot_end" SUBSYSTEM!="net", GOTO="net_name_slot_end" NAME!="", GOTO="net_name_slot_end" ENV{ID_NET_NAME_ONBOARD}!="", NAME="$env{ID_NET_NAME_ONBOARD}" ENV{ID_NET_NAME_SLOT}!="", NAME="$env{ID_NET_NAME_SLOT}" ENV{ID_NET_NAME_PATH}!="", NAME="$env{ID_NET_NAME_PATH}" LABEL="net_name_slot_end" -- and of course reboot. Seems that this is how upstream fixed the issue with the network devices, can't say it's working as in VirtualBox it doesn't, but maybe on a physical system it does. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.