What process is using 169.254.183.139

Adding the noipv4ll did solve the issue. See also https://github.com/NetworkConfiguration/dhcpcd/issues/330

Looking at the syslog at the boot phase it seems that bringing up the network interfaces seem to be to early in the boot sequence.
Bringing up WAN ( eth0) fails first time, no carrier. After LAN (eth1) is brought up, the WAN interface is tried again successfully.

1 Like