Re: Running scripts after networkd has done its things

[Tomasz Torcz <tomek@xxxxxxxxxxxxxx>]

On Fri, Jul 24, 2020 at 04:44:04PM -0400, John Ioannidis wrote:
> I'm trying to be a good boy and migrate as much functionality as I can to
> networkd.
> 
> I'm happy with how networkd manages "internal" and "external" interfaces
> and vlans for just setting up IPv4 addresses, but I still find support for
> IPv6 to be woefully inadequate, at least for my environment;
> netfilter/ipfilter support is also too rudimentary. What would be the
> "correct" (whatever that means!) way to run scripts after networkd has
> finished coming up, and before it has started going down? Essentially, I
> want to emulate the up/down feature of ifupdown.

  You may want to look at
  https://gitlab.com/craftyguy/networkd-dispatcher

  Please note, this isn't part of systemd project.  It's 3rd party software.


-- 
Tomasz Torcz               “Never underestimate the bandwidth of a station
tomek@xxxxxxxxxxxxxx        wagon filled with backup tapes.”  — Jim Gray

_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel