Re: processing order for configuration files in /etc/network/interfaces.d
On Sun 26 Aug 2018 at 21:36:30 (+0300), Martin T wrote:
> Hi David,
> > You need to post your evidence, starting with your /etc/network/interfaces
> > file. You say you're using ifup, so we can perhaps discount this paragraph:
> > Currently, "source-directory" isn't supported by
> > network-manager and guessnet.
Actually, I haven't quite figured out what this means. AIUI if an
interface is defined in /e/n/i then NM shouldn't configure it anyway.
Does it mean that if you define one in a "source-directory" directory,
NM won't realise and so might try to configure it itself?
> > but we don't know whether you're using "source-directory" or "source",
> > for example.
> I'm using "source":
> # cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> source /etc/network/interfaces.d/*
> > If you care about the order in which these files are sourced,
> > for the time being I would source them individually in the order you
> > want.
> Yes, this is probably a good idea. However, ideally, "man interfaces"
> should state in which order files in /etc/network/interfaces.d/ are
We also need to look at your evidence as to the configuration order
actually executed. I'm not yet convinced that your /tmp/interfaces_test
tells the right answer in view of the following statement:
"When ifupdown is being called with the --all option, before doing
anything to interfaces, if calls all the hook scripts (pre-up or
down) with IFACE set to "--all", LOGICAL set to the current value
of --allow parameter (or "auto" if it's not set), ADDRFAM="meta"
and METHOD="none". After all the interfaces have been brought up
or taken down, the appropriate scripts (up or post-down) are
That includes ifup -a of course.