Łukasz Wąsikowski <luk...@wasikowski.net> wrote in <51e53ac7.1040...@wasikowski.net>:
lu> hr> # IPv4 address range spec. Now deprecated.
lu> hr> ipv4_addr_em0="10.2.1.1-10"
lu>
lu> So I'm a little confused now :) If I'd use post r252015 system then
lu> would this be better way?
lu>
lu> ifconfig_em0_aliases="inet 10.0.0.66/28 inet 10.0.0.67-78 inet6
lu> fdda:5cc1:23:4::1/48 inet6 fdda:5cc1:23:4::2-f"
"Dewayne Geraghty" <dewayne.gerag...@heuristicsystems.com.au> wrote
in <14677223DB6D4CD48E880520725B3552@white>:
de> Sato-san,
de>
de> You have provided a very useful summary of ifconfig parameters for
de> rc.conf. However, you are missing one example that would provide
de> clearer understanding. Would you please advise if
de>
de> ipv4_addr_em0="10.2.1.1-10/32"
de>
de> is deprecated, backward compatible or remains valid into the future?
de>
de> I particularly appreciate the succinctness of:
de> ifconfig_em0_aliases="inet 10.3.3.201-204/24 inet6
de> 2001:db8:210-213::1/64 inet 10.1.1.1/24"
The recommended way is ifconfig_IF_aliasN or ifconfig_IF_aliases.
ipv4_addr_IF will not be removed in the near future, but please use
ifconfig_IF_alias{N,es} for newly-configured systems. Backward
compatibility for not breaking the existing configurations will be
maintained as much as possible (even on the upcoming 10.0R and
later).
This is because we have a lot of variables which have (almost) the
same functionality in rc.conf and I want to simplify them by merging
them with each other, not because these are better than the others.
Variables with overlapped functionality have made difficult to
maintain/improve the rc.d scripts.
-- Hiroki
pgpzCODgf7YuF.pgp
Description: PGP signature
