On Wed, May 8, 2024 at 1:54 PM Jonas Kvinge wrote:

Hi,

I'm using the following kernel parameters to enable networking and SSH so the LUKS encrypted root partition can be unlocked remotely in case automatic unlocking fails:

net.ifnames=0 rd.neednet=1 ip=192.168.250.20::192.168.250.200:255.255.255.0::eth0:off

When the system is booted, it's supposed to use NetworkManager and switch to another IP address, but this does not happen automatically. NetworkManager is connected to a connection named "eth0", which has automatically been created, instead of the actual network connection I've added.

This explains what happens https://lists.freedesktop.org/archives/networkmanager/2024-April/000277.html

Setting a priority on the connection does not make it switch either.

I've tried adding a systemd service to reset the network address on the interface before NetworkManager is started, the service is started on boot, but it still uses the eth0 connection with the IP address set by the kernel.

The service looks like this:

[Unit] Description=Release Network Address Before=network-pre.target

[Service] Type=oneshot ExecStart=/usr/local/bin/network-reset.sh

[Install] WantedBy=network-pre.target

In /usr/local/bin/network-reset.sh I've tried the following:

"ip addr del 192.168.250.20 dev eth0"

and

"ip addr flush eth0"

You also need to delete the run-time connection profile left over from initrd.

I've also tried "ip link set eth0 down" and "ip link set eth0 up" and various combinations of the above.

Redhat has a issue for the same thing here: https://bugzilla.redhat.com/show_bug.cgi?id=1787021

But the solution at https://access.redhat.com/solutions/3017441 seem to be closed to commercial users.

Jonas