Looks like it is a systemd bug that was fixed in later versions, I've upgraded systemd and the issue didn't resisted
Thanks for suggesting it Dagg > Sent: Tuesday, June 03, 2025 at 7:58 AM > From: "Andrei Borzenkov" <arvidj...@gmail.com> > To: "daggs" <da...@gmx.com> > Cc: systemd-devel@lists.freedesktop.org > Subject: Re: [systemd-devel] accepting dhcp address only from a specific mask > > 02.06.2025 19:36, daggs wrote: > >> Sent: Monday, June 02, 2025 at 7:09 PM > >> From: "Andrei Borzenkov" <arvidj...@gmail.com> > >> To: "daggs" <da...@gmx.com> > >> Cc: systemd-devel@lists.freedesktop.org > >> Subject: Re: [systemd-devel] accepting dhcp address only from a specific > >> mask > >> > >> 02.06.2025 18:30, daggs wrote: > >>> Greetings Andrei, > >>> > >>> here: > >>> $ ip r > >>> 0.0.0.0 dev enp1s0 scope link > >>> default dev enp1s0 scope link > >> > >> Those two lines are most certainly a problem. If they are installed by > >> systemd-networkd, I would call it a bug. Even with IPv4 local addresses > >> they are still wrong. > > > > how can I test it? > > You can disable systemd-networkd.service (and I guess .socket), check > the networking state after boot then start systemd-networkd.service and > check again. > >
