Date: Tue, 07 Feb 2012 22:32:38 +0100 From: Dirk Engling <erdgeist@erdgeist.org> To: Hiroki Sato <hrs@FreeBSD.org>, freebsd-rc@FreeBSD.org Subject: Re: Proposal ipv6_addrs_common Message-ID: <4F319876.3040303@erdgeist.org> In-Reply-To: <4F3190E6.6010405@erdgeist.org> References: <20120207.072925.1861639312875773760.hrs@allbsd.org> <4F3088C8.9090505@erdgeist.org> <20120207.170255.161251905285915806.hrs@allbsd.org> <20120207.232417.487789017555472392.hrs@allbsd.org> <4F3190E6.6010405@erdgeist.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07.02.12 22:00, Dirk Engling wrote: > Now about your loop in ifalias_af_common: if your ever encounter > an entry with no value in inet|inet6|ipx), you will keep building > up your _tmpargs forever, without any chance of ever breaking out > of this state. Ahh, now I see where this is going... you plan on collecting even more parameters to support statements like this: inet 192.168.2.1 netmask 0xffffff00 inet6 ::4 prefixlen 64 while I had constructs in mind that speak for themselves: 192.168.2.1/24 ::4/64 or maybe more verbose 192.168.2.1/24 inet6 ::4/64 ... So: is there anything besides the netmask you expect to appear in the ipv4_addrs_IF and ifconfig_IF_alias* variables? If not, we should just parse them appropriately. erdgeist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAk8xmHYACgkQuN1wFypsMNPGMACfV8F77kZGo9jVlLybz/kzHuzn QcUAnA+1gRsAtLyNqk1Zs/QURGSWYhML =5zUD -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F319876.3040303>