Package: ifupdown
Version: 0.8.10
Severity: wishlist

I decided to cross-post a bug from a Launchpad user Richard Huddleston.
He writes:

We have several custom networking scripts, and find it would be easiest
to handle them with a custom "method" in "/etc/network/interfaces".
We can't just add scripts to if-up.d, because we need strong ordering of
command execution. Examples would be adding macvlans, and ip tunnels.
For example, we need pre-up in "/etc/network/interfaces" to run before
ANY other script, because we do an ip link creation there. There are
built-in "methods" which cover some of the functionality we want, but
clearly this doesn't scale like a plugin based architecture would.
Unfortunately, there is no easy way to plug in a custom method for
handling these networking stanzas. Thus, we have to write stuff like
this for each interface.

auto vmac-ha
iface vmac-ha inet manual
        [ NORMAL ENTRIES ]
        pre-up my-vmac-helper
        up my-vmac-helper
        down my-vmac-helper
        post-down my-vmac-helper

It would be MUCH easier to have something like this

auto vmac-ha
iface vmac-ha inet custom my-vmac-helper
        [ NORMAL ENTRIES ]

Reply via email to