[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [PATCH] ifupdown: support 'link' address family
From:       Kaarle Ritvanen <kaarle.ritvanen () datakunkku ! fi>
Date:       2014-01-21 17:54:54
Message-ID: alpine.LFD.2.10.1401211944160.31869 () kunkku ! net
[Download RAW message or body]

On Sun, 29 Dec 2013, Kaarle Ritvanen wrote:

> Does not configure anything. L2 configuration hook scripts should do
> their job on receiving ADDRFAM=link. Configuration will be done only
> once, irrespective of L3 protocols used.
>
> Using the 'link' family in the interfaces file conforms to the Debian
> implementation:
>
> http://sources.debian.net/src/ifupdown/0.7.47.1/link.defn

There were no comments so far on this patch.

My intention was to allow separating the link layer configuration from the 
IPv4 (inet) and IPv6 (inet6) configuration blocks in the interfaces file 
in a way that is compatible with the Debian implementation. Do you think 
this makes sense?

Ideally, the ifupdown applet would have built-in support for configuring 
bonding, bridges, VLANs etc., but for the time being, I plan to use hook 
scripts for these purposes.

BR,
Kaarle
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic