network.subr _aliasN handling
Jason Hellenthal
jhellenthal at dataix.net
Wed Jan 1 06:14:48 UTC 2014
> On Dec 31, 2013, at 23:20, Darren Pilgrim <list_freebsd at bluerosetech.com> wrote:
>
>> On 12/27/2013 9:53 PM, jhellenthal at dataix.net wrote:
>> Looking at _alias'N' sequentialy feels like a neucense.
>
> It is. It's also very easy to overlook a gap and have the system break on a reboot. I thought ipv4_addrs_* was a good solution.
>
Ipv4_addrs var while nice can get very lengthy very quick and then more prone to humanized errors. If you add ipv6 in there it grows horizontally tenfold.
There just isn't an easy way around this unless we were to for say . . .
/etc/ifconfig_ipv4
/etc/ifconfig_ipv6
And then read in the lines one by one as . . .
$INTERFACE $ADDR $OPTS
Personally I like the way Debian handles this but I really only see a need for handling it the initial way I wrote about non-sequentially which puts it fairly close to how they do it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6118 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20140101/5061e6c6/attachment.bin>
More information about the freebsd-net
mailing list