Messages

If it works for you right now better wait for a while. No need to change anything.

Will do, I appreciate the feedback.

I apologize if I've missed something in this thread but I'm not sure how best to implement my current IPV6 DHCP setup with Kea or dnsmasq.

My current IPV6 setup is based on this guide: https://github.com/lilchancep/att-pfsense-ipv6

In short, when my WAN interface is configured to run a script which requests IPV6 prefixes from AT&T to be delegated for each my my vlans. Each VLAN interface uses the "Tracking" option for IPV6 to determine its delegated prefix. I believe selecting "Tracking" means that SLAAC is used to determine addresses for each device but I may be wrong. Is there a way in Kea or dnsmasq to duplicate this functionality or is it best that I sit tight until the dust settles on the changes that are being worked on?

In the most basic IPv6 setup you only need Router Advertisements, these will allow your clients to generate a SLAAC address, the default gateway, and you can also get a DNS server option.

DHCPv6 is when you want to hand specific addresses and options to the clients that RA cannot do.

So for you probably only RA is important.

That makes sense, I'm guessing it would work for AT&T Prefix delegation scenarios like this https://github.com/lilchancep/att-pfsense-ipv6, right?

I got the same thing, nothing is broken but it has piqued my curiosity.