Date: Thu, 20 Jun 2019 16:56:37 -0700 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: Michael Sierchio <kudzu@tenebras.com> Cc: "freebsd-ipfw@freebsd.org" <freebsd-ipfw@freebsd.org> Subject: Re: Look for an ipfw example using NPTv6 Message-ID: <49eafae6-d8bc-da6c-27c6-419252dccd2e@bluerosetech.com> In-Reply-To: <CAHu1Y70oavnHz0sL05J8v9BeKHV_Rs%2Bu6NUEXEiT0qVJXn8USQ@mail.gmail.com> References: <CAHu1Y72ezsU-f7WbYpH3h0Qcj1uttCsnQHqFue9F9xJmOtZd=w@mail.gmail.com> <3629aeba-61ef-2cce-4971-c3a0ed973765@rlwinm.de> <CAHu1Y70oavnHz0sL05J8v9BeKHV_Rs%2Bu6NUEXEiT0qVJXn8USQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-06-20 7:35, Michael Sierchio wrote: > Oh, the problem is simply that my ISP assigns me a ::/64 but there is no > guarantee that it's mine for the duration. You can work around this by using link-local addresses in your local DNS horizon, and just let devices on your network autoconf out of the dynamic /64. I have a similar arrangement with Comcast, and dhcp6+rtadvd handles allocation changes flawlessly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49eafae6-d8bc-da6c-27c6-419252dccd2e>