I’ve set-up a static IP address for my system. But upon boot my system gets assigned a DHCP IP address from the router. I get assigned 2 IP addresses:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 1c:87:2c:74:63:7d brd ff:ff:ff:ff:ff:ff
inet 201.7.5.121/24 brd 201.7.5.255 scope global dynamic noprefixroute enp4s0
valid_lft 6922sec preferred_lft 6922sec
inet 201.7.5.100/24 brd 201.7.5.255 scope global secondary enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::d48d:a025:f189:555f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
In my router the MAC address is bound to the corresponding IP address. This config / set-up worked correctly with 42.3. With my server (42.3) I have no issue with the static IP address as that works correct and that configuration is the same (except for the IP) as I use on my desktop.
I’m expecting only a single IP address and not 2. Where can I see what config is triggering the request for the DHCP (.121) provided IP address?
Also,
That’s really odd that “noprefixroute” is an attribute of your IPv4 DHCP address.
AFAIK that should only be associated with and make sense for IPv6 addressing.
Was this immediately after a manual configuration?
Besides the Wicked vs NM question, are you configuring your static address in YaST or NM, editing your interface files directly or implementing some other configuration alternative like /etc/sysctl?
And, did you restart your network service or reboot immediately after making your changes and only then run “ip addr”?
Network is using Wicked already and that is configured to be static, though I don’t have a single static IP, but 2.
Today I figured out this weird config is due to some update in TW. As I have transmission on my server whitelisted my desktop pc, but I could not access it as my IP had changed. And I did not have that problem before.
It may be disabled, but it is active.
Please show “systemctl cat NetworkManager.service” and additionally “systemctl show -p WantedBy -p RequiredBy NetworkManager”.
May be, but your own output confirms that NetworkManager is running which is likely responsible for the second IP. The question is why it is started.