05.07.2019 16:18, Simone Piccardi wrote:
Package: tinc
Version: 1.0.35-2
Severity: normal
Dear Maintainer,

when starting tinc on a server using bridges as main interfaces (it's
used to run VM) it starts but it fails in the up script execution to
setup network routes, because interfaces are still not up (on bridge
it takes a while to go up), and you need them up if you need to setup
a specific route source for use on tinc network.

As systemd documentation says you need to use network-online.target
and not network.target to have this, as it was with jessie. This is
broken in squeeze and in buster also.
The fun thing here is that for one, I use tinc in exactly the opposite
way, so it _provides_ network-online.target, -- I need it to start and
connect to office before I declare network to be fully up.

I _think_ in your case you can add a systemd dependency rule so that
tinc starts after the particular bridge, instead of requiring network
to be online before starting tinc. However it is not clear to me if
this is easily done without moving network management to
systemd-networkd from /etc/network/interfaces.

BTW, the same "duality" is known to exist with other services. For
example, sometimes a nameserver needs network to be fully up before
it can answer queries and answering queries _needs_ to be done
_to_ bring network up (eg tinc might need to know an IP of the other
peers). Sometimes this stuff can be funny.

/mjt

Reply via email to