With the Tumbleweed snapshot 20150225 a wrong patch for the udevrules was
applied.  This results in the device names of network interfaces changing if
they are using biosdevnames and consequently loss of network connectivity at
the next boot.

The change was:
--8<---------------cut here---------------start------------->8---
snapper diff 912..913 /usr/lib/udev/rules.d/71-biosdevname.rules
--- /.snapshots/912/snapshot/usr/lib/udev/rules.d/71-biosdevname.rules 
2015-01-31 01:53:06.000000000 +0100
+++ /.snapshots/913/snapshot/usr/lib/udev/rules.d/71-biosdevname.rules 
2015-02-25 03:25:27.000000000 +0100
@@ -15,13 +15,14 @@
 ENV{UDEV_BIOSDEVNAME}=="0", GOTO="netdevicename_end"
 ENV{UDEV_BIOSDEVNAME}=="1", GOTO="netdevicename_start"

-# uncomment the next line for biosdevname to be off by default
+# comment the next line for biosdevname to be on by default
 GOTO="netdevicename_end"

 LABEL="netdevicename_start"

 # using NAME= instead of setting INTERFACE_NAME, so that persistent
 # names aren't generated for these devices, they are "named" on each boot.
-SUBSYSTEMS=="pci", PROGRAM="/sbin/biosdevname --policy physical --smbios 2.6
--nopirq -i %k", NAME="%c",  OPTIONS+="string_escape=replace"
+SUBSYSTEMS=="pci", PROGRAM="/sbin/biosdevname --policy physical --smbios 2.6
+ --nopirq -i %k", NAME="%c",  OPTIONS+="string_escape=replace"

 LABEL="netdevicename_end"
--8<---------------cut here---------------end--------------->8---

Not the line-wrapping introduced.  If I remove that linewrap, things are back
to normal.