There is some documentation around how to implement this with netplan
here: https://netplan.io/faq/#use-pre-up%2C-post-up%2C-etc.-hook-scripts
But its basically using the underlying renderer's (NM or networkd-
dispatcher) hooks, as netplan itself is not a networking daemon and
cannot easily
To my knowledge, networkd-dispatcher has no way to do 'pre' hooks on
systemd-networkd events, so this is still a valid feature request.
** Changed in: systemd (Ubuntu)
Status: Invalid => Triaged
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-17.05 => None
** Changed in: systemd
marking this as invalid for systemd as arbitrary code can be run using
networkd-dispatcher and/or suggestions from comment 4.
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I too have special action rely on these commands, mainly
inserting/removing iptables rule and/or creating virtual sub-interfaces.
While this most likely able to be achieved by systemd, but learning
systemd itself requires time. It will be wise for netplan to incorporate
these functionality
I need to add routing information to one interface to allow ssh that
enters via the non-default gateway. Before metalanguage this was easy.
Now it's so difficult! The closest advice was networkd-dispatcher but
the advised directory doesn't exist. I can't see why "legacy"
functionality is
You mention that all the examples can already be done by netplan, yet
one, he mentioned was modifying iptables, something I use myself, and
have yet to find that anywhere in netplan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm kind of concerned about any non-declarative functionality here. For
example, DHCP client and receiving/updating routes are all handled by
netwokrd already.
You can bind a systemd unit to e.g. sys-subsystem-net-devices-
eth0.device and then any number of systemd units should be started and
> The requirement here is, I need to know when ens1 goes up or down, so
> that I can make changes to the bridge interface. The `ifmonitor` script
> will monitor the link status of ens1, and then take appropriate actions,
> such as restarting a DHCP client, adding or removing routes that have
>
