Date: Wed, 19 Aug 2015 15:06:32 -0600 From: John Nielsen <john@jnielsen.net> To: Gary Palmer <gpalmer@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: RFC7084 "Basic Requirements for IPv6 Customer Edge Routers" Message-ID: <2B3FA2D7-B0A9-4489-A65B-A6E8630DE62F@jnielsen.net> In-Reply-To: <20150817112408.GB13503@in-addr.com> References: <20150817112408.GB13503@in-addr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Since FreeBSD is a general-purpose operating system, a fresh install = with default options will certainly not meet all the requirements. = However, from a quick read of the RFC it looks like it would be = straightforward to configure a FreeBSD box to meet the requirements. For simple routing, the include rtadvd(8) may be adequate; however I am = unsure if its behavior by default would meet req G-4 from 4.1. (If it = doesn=E2=80=99t, a small script to add interfaces using rtadvctl once = appropriate WAN routes are available would suffice.) FreeBSD does = include a RIP6 routing daemon (route6d); other routing protocols are = supported by third-party programs such as quagga or openbgpd. FreeBSD supports SLA but requires third-party software for DHCP6 client = or server operation. Examples of such software include dhcp6, = isc-dhcp43-client, and isc-dhcp43-server. Those are all the potential sticking points that stood out to me. On Aug 17, 2015, at 5:24 AM, Gary Palmer <gpalmer@freebsd.org> wrote: >=20 >=20 >=20 > Hi, >=20 > Does anyone know if FreeBSD 9.3 is compliant with RFC7034? =20 >=20 > Thanks, >=20 > Gary > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2B3FA2D7-B0A9-4489-A65B-A6E8630DE62F>