On Sat, Feb 25, 2023 at 09:42:49AM +0700, Max Nikulin wrote:
> On 25/02/2023 04:43, Geert Stappers wrote:
> > Having `apt purge avahi-autoipd` still gets me "auto IPv4 address"
> >
> > Ideas how to avoid it are welcome.
>
> Have you checked "journalctl --boot" for logs which component assigns
> 169.254.x.y address and for various errors related to network?
Just did (checking `journalctl --boot`) and found lines like
Feb 24 22:24:13 trancilo systemd-networkd[455]: ovs-system: Unmanaging
interface.
Feb 24 22:24:13 trancilo systemd-networkd[455]: ovs-system: State changed:
initialized -> unmanaged
Feb 24 22:24:14 trancilo dhcpcd[1175]: ovs-system: waiting for carrier
Feb 24 22:24:14 trancilo systemd-networkd[455]: ovs-system: IPv6 link-local
address generation mode is changed: eui64 -> none
Feb 24 22:24:14 trancilo systemd-networkd[455]: ovs-system: Flags change: +UP
+LOWER_UP +RUNNING
Feb 24 22:24:14 trancilo systemd-networkd[455]: ovs-system: Link UP
Feb 24 22:24:14 trancilo systemd-networkd[455]: ovs-system: Gained carrier
...
Feb 24 22:24:14 trancilo NetworkManager[1188]: <info> [1677273854.7167]
manager: (ovs-system): new Generic device
(/org/freedesktop/NetworkManager/Devices/3)
Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: carrier acquired
Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: IAID cb:93:09:25
Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: adding address
fe80::56b2:83e1:5ceb:9d50
...
Feb 24 22:24:16 trancilo dhcpcd[1175]: ovs-system: soliciting a DHCP lease
...
Feb 24 22:24:21 trancilo dhcpcd[1175]: ovs-system: probing for an IPv4LL address
Feb 24 22:24:26 trancilo dhcpcd[1175]: ovs-system: using IPv4LL address
169.254.201.7
Feb 24 22:24:26 trancilo dhcpcd[1175]: ovs-system: adding route to
169.254.0.0/16
Feb 24 22:24:26 trancilo systemd-networkd[455]: ovs-system: Received new
foreign address (configured): 169.254.201.7/16 (valid forever, preferred
forever), flags: permanent,no-prefixroute, scope: global
Feb 24 22:24:26 trancilo dhcpcd[1175]: ovs-system: adding default route
Feb 24 22:24:26 trancilo systemd-networkd[455]: ovs-system: link_check_ready():
link is in unmanaged state.
Feb 24 22:24:26 trancilo systemd-networkd[455]: ovs-system: Received new
foreign route (configured): dst: 169.254.201.7/32, src: n/a, gw: n/a, prefsrc:
169.254.201.7, scope: host, table: local(255), proto: kernel, type: local,
nexthop: 0, priority: 0, flags: n/a
Feb 24 22:24:26 trancilo systemd-networkd[455]: ovs-system: Received new
foreign route (configured): dst: 169.254.255.255/32, src: n/a, gw: n/a,
prefsrc: 169.254.201.7, scope: link, table: local(255), proto: kernel, type:
broadcast, nexthop: 0, priority: 0, flags: n/a
> I am not familiar with openvswitch (or another package that really created
> ovs-system and ovsbr0), so I have no idea how they may be configured
> (systemd-networkd, NetworkManager, netplan, ifupdown) in your case and how
> to configure them properly. Perhaps it better to ask their community how to
> avoid failure of systemd-networkd-wait-online and assigning of IPv4LL
> address.
AIUI is systemd-networkd the main player, dhcpcd some helper
and NetworkManager for contact with user.
> I have realized that your problem may be more general than just ovs-system,
> I do not like the following log line and which file is not found is not
> clear for me:
> > feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: wlan0: Failed
> > to update link state, ignoring: No such file or directory
>
Acknowledge on the "be aware of a problem with wlan0"
Groeten
Geert Stappers
--
Silence is hard to parse
