david rankin wrote:
The problem seems to be in /etc/udev/rules.d/30-net_persistent_names.rules. The question [bug] is how in the heck duplicate entries got created in the first place.
Yep, I would report that to Novell - bugzilla.novell.com. Especially given that some apparently bogus MAC-address is found and entered.
Something in SuSE setup must have created the first entry. Of course, the hardware address is wrong, but for some reason it is there. As noted, this must be a popular MAC address given the 372 references to it on Google.
And as "a popular MAC address" is clearly oxymoronic, it's gotta be a bug. Maybe someone decided to conjure up a "hidden" MAC-address for some or other purpose, and it got lose?
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:4c:69:6e:75:79", IMPORT="/sbin/rename_netiface %k eth0" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:04:5a:87:c8:43", IMPORT="/sbin/rename_netiface %k eth1"
I would just edit this file so you're left with: SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:04:5a:87:c8:43", IMPORT="/sbin/rename_netiface %k eth0" I still don't understand why an 'eth1' is even mentioned during startup, but ...
Reading the list, I know I'm not the only poor sucker that has pulled his hair out over this problem. The problem seems to be that somewhere during initial setup, if Yast can't guess the right driver or MAC for the NIC, it makes one up that will work.
Something like that - but I don't think it's YaST, given how often that particular MAC address is referenced on various mailing-lists. /Per Jessen, Zürich (-5.75 °C) -- http://www.spamchek.com/ - managed anti-spam and anti-virus solution. Let us analyse your spam- and virus-threat - up to 2 months for free.