On 2021 Nov 15 (Mon) at 13:58:08 +0100 (+0100), Claudio Jeker wrote:
:On Mon, Nov 15, 2021 at 12:23:02PM +0000, Klemens Nanni wrote:
...
:Sure people got used to this mode. I agree with dlg@ that the way that
:this auto interface up happens is rather horrible from a network stack
:view. Also it makes it impossible to configure an interface all the way
:before bringing it up. This may be important for interfaces with more
:complex configuration.
:
:The current behaviour is great for casual users (that does not really
:care about network) but is annoying for network admins.
:
This behaviour caused no ends of problems for me when I was
administering carp interfaces with several / many IPs assigned to them.
Extremely painful to add multiple addresses to the carp cluster.
:> > I've suggested previously that netstart should handle bringing an
:> > interface up. look for "netstart: implicit up and explicit down for
:> > hostname.if conf files" on tech@. I didn't hanve the energy to push
:> > it forward though.
:>
:> I'll do the digging and try to catch up, thanks.
:
:Another option is to adjust ifconfig but then again one would like to do
:the up last after running multiple ifconfig calls. ifconfig has its own
:madness when it comes to execute multiple commands in one go.
:
That will address several situations, but I don't know if it covers
all / enough of them.
:> > dhcpd should cope with an interface being down too. It should be about
:> > whetherthe addresses are right more than if the interface is up or not.
:
:I expect an interface that is down to remain down until I bring it up
:again. Same goes the other way. ifconfig up/down should only be used to
:implement admin shutdown. We fixed a few interfaces in the past that
:played with IFF_UP in the driver.
:
100% yes
:--
::wq Claudio
:
--
The plot was designed in a light vein that somehow became varicose.
-- David Lardner
