Date: Sat, 26 Jun 2021 21:02:35 -0500 From: Louis Kowolowski <louisk@cryptomonkeys.org> To: Doug Hardie <bc979@lafn.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: IPv6 Sub Nets Message-ID: <B707A230-78B3-4BF8-B7C0-350E48EAEF04@cryptomonkeys.org> In-Reply-To: <056639D1-32A2-4DAF-A6F8-C8743F691EAD@sermon-archive.info> References: <056639D1-32A2-4DAF-A6F8-C8743F691EAD@sermon-archive.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 26, 2021, at 8:25 PM, Doug Hardie <bc979@lafn.org> wrote: > > I am trying to setup an IPv6 environment. There is a primary router (A) that receives a /48 prefix via DHCP6 from the ISP. That router configures itself properly via dhcp6c. It also creates 2 LAN /64 prefixes and creates EUI-64 addresses on the two LAN interfaces. One of those interfaces is connected to a second router (B), among other devices. The B router receives the prefix via SLAAC and creates its own EUI-64 address. However, that router needs to create a smaller subnet, /72, and distribute it to the devices on that LAN. I have not been able to figure out how to make that happen. > > Clearly, manual configuration would work, but the prefix received from the ISP can change which would raise havoc with the network. I suspect that dhcp6s needto be run alongside dhcp6c on router B and then the other devices run dhcp6c. However, I don't see how to get the prefix that dhcp6c receives on router B to the dhcp6s process on router B. I believe I am missing something, but haven't been able to find it. Thanks, > Speaking generally First: I believe you’re looking to do DHCP prefix delegation (dhcp-pd) where you designate a prefix to be used further down the line. Second: There are valid use cases for prefixes smaller than /64, but they are not best practice, and you will likely find software that doesn’t work for them (examples I’ve found include PDUs hardcoding /64, dhcp not working on prefixes smaller than /64. examples of things I’ve seen that do work: point-to-point links on network equipment using /126 or /127). -- Louis Kowolowski louisk@cryptomonkeys.org <mailto:louisk@cryptomonkeys.org> Cryptomonkeys: http://www.cryptomonkeys.com/ <http://www.cryptomonkeys.com/>; Making life more interesting for people since 1977
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B707A230-78B3-4BF8-B7C0-350E48EAEF04>