https://bugzilla.novell.com/show_bug.cgi?id=853762 https://bugzilla.novell.com/show_bug.cgi?id=853762#c0 Summary: Random Ethernet MAC address reassignment after system power event (unplug) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ar16@imapmail.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 I have a serer with 2 Eth interfaces. eth0 (sky2) is for external/net connection. eth1 (r8169) is for internal/lan connection. For the entire OS 12.x cycle, udev (mis)naming & random MAC address changes on reboot, power outage, etc were kept in check with: cat /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:52:35:d9:43:36", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:43:00:41:5e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" cat /etc/udev/rules.d/99-mac-address.rules SUBSYSTEM=="net", KERNEL=="eth0", RUN+="/sbin/ip link set dev %k address 00:52:35:d9:43:36" SUBSYSTEM=="net", KERNEL=="eth1", RUN+="/sbin/ip link set dev %k address 00:50:43:00:41:5e" That config survived countless reboot events -- planned & unplanned, including random testing by unplugging the machine while booted and functional. Upgrading the server from 12.3 -> 13.1, that config survived as well. Controlled/manual reboots had no issues. However, after an 'unplug power' test, the network fails. dmesg shows that eth0 is suddenly recognized as a dramatically different MAC addr ... #[ 25.371651] r8169 0000:03:00.0 eth0: RTL8168c/8111c at 0xffffc9000006e000, 08:52:35:59:53:77, XID 1c4000c0 IRQ 47 ... changing, cat /etc/udev/rules.d/70-persistent-net.rules - SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:52:35:d9:43:36", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" + SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:52:35:d9:43:36", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:43:00:41:5e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" and cat /etc/udev/rules.d/99-mac-address.rules - SUBSYSTEM=="net", KERNEL=="eth0", RUN+="/sbin/ip link set dev %k address 00:52:35:d9:43:36" + SUBSYSTEM=="net", KERNEL=="eth0", RUN+="/sbin/ip link set dev %k address 08:52:35:59:53:77" SUBSYSTEM=="net", KERNEL=="eth1", RUN+="/sbin/ip link set dev %k address 00:50:43:00:41:5e" Prior to the 12.x cycle, and the udev rules I'd created to avoid the problem, I'd occassionally see small incremental changes in MAC, e.g from 00:52:35:d9:43:36 to 00:52:35:d9:43:37 The current change from 00:52:35:d9:43:36 to 08:52:35:59:53:77 appears quite significant, changing even the (unlisted) OUI There's a similar bug for 12.3, @ https://bugzilla.novell.com/show_bug.cgi?id=809843#c24 wherein it's stated "The next release of openSUSE will contain all necessary parts (net_id, hwdb) sowe can really drop persistent rules, but until then don't think there is another way." The implication is for 13.1 there's another method needed/available. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.