Bug#1000510: systemd: all server programs fail when they are set to specified interfaces

Michael Biebl biebl at debian.org
Mon Jul 4 14:11:05 BST 2022


On Fri, 26 Nov 2021 00:57:09 -0500 westlake <westlake2012 at videotron.ca> 
wrote:
> there is new criteria I can add to this original bugreport:
> 
> here I did additional tests and noticed new light of observations that 
> your override does not take effect for ifupdown(networking.service), 
> even though it should by the information you have provided.
> 
> the summary I can make of things so far regarding this is,
> 
> 1) the override (from your suggestion of After=, Wants=)   only works 
> only when the user opts to adopt "systemd-networkd"
> and

I'm pretty sure it works with NetworkManager as well (which provides 
NetworkManager-wait-online.service, which hooks into network-online.target).

> 2) the override does nothing when the user stays with the default 
> networking.service (it is supposed to but it doesn't)
> 
> ^ According to you the systemd override should work whether the user 
> uses networking.service or systemd-networkd -- but this isn't happening.
> 

Well, obviously networking.service (as provided by ifupdown) needs to 
hook into network-online.target for this target to be useful.

Please read the documentation at https://systemd.io/NETWORK_ONLINE/

In case of ifupdown, you probably want to enable 
ifudpown-wait-online.service or use type auto.
That said, I don't use ifupdown anymore, so can't really help you with 
its configuration.


Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220704/6a5f22e1/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list