Re: Remove route '169.254.0.0/16 dev ovs-system'
On Sun 26 Feb 2023 at 22:11:30 (+0700), Max Nikulin wrote:
> On 26/02/2023 18:18, Geert Stappers wrote:
> > AIUI is systemd-networkd the main player, dhcpcd some helper
> > and NetworkManager for contact with user.
>
> First of all, I would not touch dhcpcd.conf for a while.
>
> Is it assumed that ovs-system should get its IP address from DHCP?
>
> If I understand it correctly, systemd-networkd may send DHCP request
> itself, it does not need dhcpcd helper.
Yes, if you configure it to, eg:
# /etc/systemd/network/80-wifi.network for systemd-networkd last edited 2022-09-30
[Match]
Name=wl*
[Network]
DHCP=ipv4
IgnoreCarrierLoss=true
[DHCPv4]
RouteMetric=20
#
which gave this morning (daemon.log):
avahi-daemon[359]: Joining mDNS multicast group on interface wlp2s4.IPv4 with address 192.168.1.10.
systemd-networkd[216]: wlp2s4: Gained carrier
avahi-daemon[359]: New relevant interface wlp2s4.IPv4 for mDNS.
avahi-daemon[359]: Registering new address record for 192.168.1.10 on wlp2s4.IPv4.
systemd-networkd[216]: wlp2s4: DHCPv4 address 192.168.1.10/24 via 192.168.1.1
systemd[1]: Started Getty on tty1.
systemd[1]: Reached target Login Prompts.
(man 5 systemd.network) and:
$ ip r
default via 192.168.1.1 dev wlp2s4 proto dhcp src 192.168.1.10 metric 20
192.168.1.0/24 dev wlp2s4 proto kernel scope link src 192.168.1.10
192.168.1.1 dev wlp2s4 proto dhcp scope link src 192.168.1.10 metric 20
$
> NetworkManager is not only UI,
> it may manage interfaces. I would not be surprised if more than one
> tool tries to manage ovs-system.
>
> Perhaps some of the following command may shed some light on what
> really happens:
>
> systemctl --failed
> networkctl list
> networkctl status ovs-system
This long thread seems to be turning into a game of 20 Questions.
It would be nice to see some of the OP's configuration, rather
than just a few log extracts and a "How do I get rid of …".
As it is, the OP has said "no more route 169.254.0.0/16 for device
ovs-system", so perhaps all that's left is to leave that as solved,
and tiptoe over to the alternate OP (CB) and see if they decide to
restore the removed and disabled packages (XFCE and avahi-daemon)
to check whether their 169.254.… addresses return.
> Last command should show Network File name if the interface is really
> managed by systemd-networkd. Please, post its content
>
> nmcli general status
> nmcli device
> nmcli -f CONNECTIONS device show ovs-system
>
> ifquery --list
>
> and check if /etc/network/interfaces and /etc/network/interfaces.d for
> ovs-system entries
>
> See also
> https://wiki.debian.org/NetworkConfiguration
>
Cheers,
David.
Reply to: