Comment # 4 on bug 916377 from andreas bittner

Okay I really need this machien to come back up and properly communicate via
its interfaces so I just tried to:

ifconfig enp10s0 192.168.100.254 netmask 255.255.255.0

but that gives my very weird output, it creates a virtual interface to that
enp10s0 as 

enp10s0:0 Link encap:Ethernet  HWaddr 48:5B:39:36:D5:43
          inet addr:192.168.100.254  Bcast:0.0.0.0  Mask:0.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


and then ifconfig suddenly displays that address as well on the main enp10s0
interface


enp10s0   Link encap:Ethernet  HWaddr 48:5B:39:36:D5:43
          inet addr:192.168.100.254  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::4a5b:39ff:fe36:d543/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:183 errors:0 dropped:2 overruns:0 frame:0
          TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17240 (16.8 Kb)  TX bytes:8179 (7.9 Kb)


But the whole network is basically completely messed up on that .100/24
interface

Help what the heck is wrong here, I feel like a beginner to networking after
this incident :(((

Before that ifconfig line to add the ip address manually it didnt display
anything ipv4 related on that enp10s0

enp10s0   Link encap:Ethernet  HWaddr 48:5B:39:36:D5:43
          inet6 addr: fe80::4a5b:39ff:fe36:d543/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:52 errors:0 dropped:1 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3806 (3.7 Kb)  TX bytes:4316 (4.2 Kb)


wicked now displays
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
      addr:     ipv4 192.168.100.254/0


In this state susefirewall2 is also messing up stuff as it is not allowing
traffic to this messed up 100.254 configuration because it is a subdevice or
something so i turned susefirewall2 off completely which helps a bit but this
is really a big mess :(