A pretty much fresh (few weeks only) 13.2 x86-64 system. Several eth
interfaces.

I applied a buch of zypper up updates (especially all those library updates and
systemd or something from the past few days make me feel weird) and rebooted
the machine.

Luckyly the external eth interface was fine, and I tried to ssh tunnel into an
internal machine to its vnc port until I relalized that the internal network
interface card was only having its default ipv6 linklocal address assigned, but
the statis ipv4 rcf1918 address wasnt assigned to it.

:( These elementary bugs and essential things really make me frustrated

All the config files that I am aware off were set way in the past so not messed
with as far as I can tell and everything worked okay when I rebooted yesterday
or some days ago, but not today any more :(

-rw-r--r--   1 root root 34789 Jan 25 23:50 SuSEfirewall2
It has the ext and int entries:
grep enp SuSEfirewall2
FW_DEV_EXT="enp4s0"
FW_DEV_INT="enp10s0"

enp4s0 is up and working and accessible and I am ssh connecting to that
interface from a remote location.

enp10s0 is only displaying the follwing:

enp10s0   Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet6 addr: fe80::4a5b:39ff:fe36:d543/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5274 errors:0 dropped:62 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:441920 (431.5 Kb)  TX bytes:4451 (4.3 Kb)



systemctl status network.service
wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
   Active: active (exited) since Thu 2015-02-05 01:39:09 CET; 10h ago
  Process: 907 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited,
status=0/SUCCESS)
 Main PID: 907 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/wicked.service

Feb 05 01:39:09 tux wicked[907]: lo              up
Feb 05 01:39:09 tux wicked[907]: enp4s0          up
Feb 05 01:39:09 tux wicked[907]: enp10s0         up


The file dates for the network interface config files are:
-rw-r--r-- 1 root root    30 Jan 25 21:57 ifroute-enp4s0
-rw-r--r-- 1 root root  8212 Jan 25 22:01 dhcp
-rw------- 1 root root   191 Jan 25 22:01 ifcfg-enp10s0
-rw------- 1 root root   189 Jan 25 22:01 ifcfg-enp4s0
drwxr-xr-x 2 root root  4096 Jan 25 22:01 scripts
-rw------- 1 root root   173 Jan 26 15:10 ifcfg-lo


and the contents are all fine

less ifcfg-enp4s0
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.2.254/24'
MTU=''
NAME='RTL8111/8168 PCI Express Gigabit Ethernet controller'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'


less ifcfg-enp10s0
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.100.254/24'
MTU=''
NAME='RTL8111/8168 PCI Express Gigabit Ethernet controller'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'



But there is no 192.168.100.254 assigned to the internal enp10s0 :((((