http://bugzilla.opensuse.org/show_bug.cgi?id=916377 --- Comment #1 from andreas bittner --- I issued a reboot and still all the same. Additionally maybe the network cable got removed or something so I checked: Link is there as well: dmesg | grep -i enp | more [ 20.360927] r8169 0000:04:00.0 enp4s0: link down [ 20.360996] r8169 0000:04:00.0 enp4s0: link down [ 20.361004] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready [ 20.547544] r8169 0000:0a:00.0 enp10s0: link down [ 20.547608] r8169 0000:0a:00.0 enp10s0: link down [ 20.547615] IPv6: ADDRCONF(NETDEV_UP): enp10s0: link is not ready [ 22.633726] r8169 0000:04:00.0 enp4s0: link up [ 22.633752] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready [ 22.860035] r8169 0000:0a:00.0 enp10s0: link up [ 22.860051] IPv6: ADDRCONF(NETDEV_CHANGE): enp10s0: link becomes ready ethtool enp10s0 Settings for enp10s0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes ethtool enp4s0 Settings for enp4s0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916377 --- Comment #3 from andreas bittner --- Also: what am I doing wrong, trying to reload the interface with: wicked ifreload enp10s0 wicked: ifreload: no matching interfaces Supported commands: ifup [options] |all ifdown [options] |all ifcheck [options] |all ifreload [options] |all wicked ifstatus enp10s0 enp10s0 up link: #4, state up, mtu 1500 type: ethernet, hwaddr 48:5b:39:36:d5:43 config: compat:/etc/sysconfig/network/ifcfg-enp10s0 leases: ipv4 static granted now apparently even some ipv6 link local stuff is gone from enp10s0, something must have changed with the ifreload command never the less is it possible that these wicked and related things are actually full of bugs? ;( -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916377 --- Comment #5 from andreas bittner --- small temporary workaround for me at the moment is: ifconfig enp10s0:0 del 192.168.100.254 ifconfig enp10s0 del 192.168.100.254 ifconfig enp10s0 down ifconfig enp10s0 192.168.100.254 netmask 255.255.255.0 up and then restart my services on enp10s0 or start them at all as they failed because there was no usable ipv4 address on it :( -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916377 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Enhancement --- Comment #7 from andreas bittner --- Okay thanks for the debug hint and here is the outcome of this whole bug. Turns out that there was a duplicate already taken static ipv4 device already on the network. I am totally confused though why it never mattered until the day I filed this bugreport. So I am sorry for filing this bugreport, but as a side effect I got to learn a bit about wicked and related stuff and I find the lack of serious warnings and more prominent representation of such bad network states and network disarray as duplicate ip addresses taken and being replied for by other mac addresses (other devices). I sorted out the other device and changed its ip address, but this device was on the network right from the start back when the opensuse 13.2 machine joined the lan back in January 2015. So please if somehow possible, really do warn the user more prominently or more often in the logs about this state. The warning message I see in journalctl regarding this matter apparently reads: Feb 05 01:39:09 tux wickedd[905]: enp10s0: address '192.168.100.254' is already in use I searched for "duplicate" or "double" or similar strings before, but the message doesnt contain such wording, and only while browsing at the endless wicked(d) debug messages I observed some line that some other mac address was already using that ipv4 static address and thus wicked or whatever layer couldnt or wouldnt keep this ip set for the opensuse machine. Still it did work all those days from january to feb5 and every now and then forcefully setting and messing with ifconfig did configure the opensuse machine to use this ipv4 address on the internal lan. Weird. Sorry again and maybe we can make use of this incident to enhance warnings, these situations and provide the user with more and speedy information during such events. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.