systemd timing

[Karl Auer]

On Sat, 2017-07-15 at 13:31 +0200, Xen wrote:
> Karl Auer schreef op 15-07-2017 13:04:
> > How can I make a systemd service run after all network interfaces
> > are up?

The actual problem was that certain IPv6-related sysctl variables were
not being set because the interfaces were up at the time the sysctl
service ran. OR the network plumbing was setting them back; that's a
possibility I was unable to check.

Specifically, autoconf was not working, and the autoconf and accept_ra
variables were not being set (or were being reset).

Running the sysctl service again manually after boot fixed the problem
temporarily, hence my desire to run it later, but automatically.

In trying to make that simple thing happen, I was exposed to the full
lunacy that is systemd.

I finally got it to work by making it dependent on a late-completion
target ("WantedBy=multi-user.target"). I was completely unable to
locate the correct moment to re-run it, so the fine-grained control
that is supposed to be enabled by systemd was made a mockery of.

The solution to my actual problem was to use static IPv6 addresses
(which is what I needed anyway, I just got distracted by SLAAC
addressing apparently not working).

There are still several anomalies WRT IPv6 addressing; I think the
presence of at least three systems, each of which seems to want to
control elements of SLAAC, is a big part of the problem. DHCP, systemd
and the "old" /etc/network/interfaces method.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A
Old fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B