On Tue, 16 Sep 2003, Pekka Savola wrote:
On Tue, 16 Sep 2003, Paul Jakma wrote:
> generic DEPENDSON parameter to specify dependencies. File to
> interface order is probably by far easiest to implement,
This is a good idea, but with more consideration, it may not be
entirely trivial in the case that DEPENDSON would have to list more
than one interface, or something generic like, "the interface the
default route points to".
yeah, thats what i reckon - trying to solve it by listing
dependencies could become quite involved i think.
The more I think of this, the more interesting this
DEPENDSON="<one-interface>"|"default" sounds; the latter would
general term to look up a default route (or something like that).
hmm.. but it might not be dependent on the default route - it might
be dependent on a specific route. (ie default goes via the ISP. But
your 'VPN' or other interface depends on the route for your vpn peer
to have been installed by ospfd or somesuch). very tricky really - i
dont think going by dependent interfaces is viable - never mind
The ordering may not always be so trivial, like "VPN
and "regular interfaces". Eth0 could be upstream while eth1 would
be intranet interface (and one could require the other), for
well, you could just list them explicitely one after the other i
Paul Jakma paul(a)clubi.ie paul(a)jakma.org Key ID: 64A2FF6A
warning: do not ever send email to spam(a)dishone.st
The first time, it's a KLUDGE!
The second, a trick.
Later, it's a well-established technique!
-- Mike Broido, Intermetrics