On Sun, Feb 19, 2023 at 12:21:36PM -0500, Stefan Monnier wrote:
> >> Having installed package openvswitch-switch and doing `ip route` I do get
> >>   169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
> >> 
> >> What can be done to prevent that "zeroconf"
> >> configures interface `ovs-system`?
> >
> > Please have a look at https://wiki.debian.org/Avahi.
> > According to the section "Disabling avahi-daemon" the following
> > commands should work:
> >
> > For permenant disablement (surviving a machine reboot):
> > systemctl mask avahi-daemon.service avahi-daemon.socket
> > systemctl disable avahi-daemon.service avahi-daemon.socket
> > systemctl stop avahi-daemon.service avahi-daemon.socket
> 
> But Avahi provides more functionality (e.g. mdns) than merely
> configuring network interfaces,
> so disabling it altogether may be undesired.

Yes, may.  And by disabling it I will find out what I miss  :-)

 
> So hopefully there's a way to keep Avahi and still avoid that interface
> being configured in such a dummy way.
> [ I thought Avahi only did such configuration as a "last recourse", so
>   there's a chance that you're only seeing the effect of another problem
>   which prevents the interface from being configured properly and
>   there's just no need to worry about preventing this dummy config:
>   just find and fix the other problem, and then Avahi won't kick in.  ]
 

Disabling  avahi did not prevent route set on device ovs-system.

My guess is that other compoments ( network-manager, systemd-networkd )
are involved.


Regards Geert Stappers


screenshot:

$ systemctl status avahi-daemon{,.socket}
○ avahi-daemon.service
     Loaded: masked (Reason: Unit avahi-daemon.service is masked.)
     Active: inactive (dead)

○ avahi-daemon.socket
     Loaded: masked (Reason: Unit avahi-daemon.socket is masked.)
     Active: inactive (dead)
$ ip route | grep ovs-system
169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
$ systemctl --failed
  UNIT                                 LOAD   ACTIVE SUB    DESCRIPTION
● systemd-networkd-wait-online.service loaded failed failed Wait for
Network to be Configured

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of
SUB.
SUB    = The low-level unit activation state, values depend on unit
type.
1 loaded unit listed.
$ systemctl status systemd-networkd-wait-online
× systemd-networkd-wait-online.service - Wait for Network to be Configured
     Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; 
enabled; preset: disabled)
     Active: failed (Result: exit-code) since Sun 2023-02-19 18:48:17 CET; 
10min ago
       Docs: man:systemd-networkd-wait-online.service(8)
    Process: 601 ExecStart=/lib/systemd/systemd-networkd-wait-online 
(code=exited, status=1/FAILURE)
   Main PID: 601 (code=exited, status=1/FAILURE)
        CPU: 32ms

feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: wlan0: Failed to 
update link state, ignoring: No such file or directory
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovs-system: Failed 
to update link state, ignoring: No such file or directory
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovs-system: Failed 
to update link state, ignoring: No such file or directory
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovsbr0: Failed to 
update link state, ignoring: No such file or directory
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovsbr0: Failed to 
update link state, ignoring: No such file or directory
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovsbr0: Failed to 
update link state, ignoring: No such file or directory
feb 19 18:48:17 trancilo systemd-networkd-wait-online[601]: Timeout occurred 
while waiting for network connectivity.
feb 19 18:48:17 trancilo systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
feb 19 18:48:17 trancilo systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
feb 19 18:48:17 trancilo systemd[1]: Failed to start 
systemd-networkd-wait-online.service - Wait for Network to be Configured.
$
-- 
Silence is hard to parse

Reply via email to