Track Interface with 26.1

[mrt12]

Good day,
so I already switched in the past away from ISC DHCPD to Kea. It seemed to work fine so far, besides the fact that Kea cannot register DHCPv4 leases in DNS. But I can live with that, I generated static entries for the most important things, so its not a huge thing.

So today I just upgraded to 26.1 and also it still seems to work fine. However, I understand from the release notes, that "Track Interface" is something that is legacy and should not be used anymore. Also in the config page of my LAN interface it reads "Track interface (legacy)". So I tried to switch to "Identity Association" which, apparently, seems to be the new thing.
However, it gives me always the error:

Code Select Expand

The DHCPv6 Server is active on this interface and it can be used only with a static IPv6 configuration. Please disable the DHCPv6 Server service on this interface first, then change the interface configuration.
I am confused, because under "Services", "Kea DHCPv6" it is disabled. Furthermore, I have uninstalled the ISC-DHCP Plugin, so to my understanding, the DHCPv6 server should not be running at all.

I think I would need this Identity Association, as I needed previously "Track Interface". This is because my ISP gives me a /56 IPv6 Prefix, and I want several subnets of it to be delegated to my different VLANs. So What do I need to change to achieve the same behaviour as before? is is it not even possible anymore?
Note that I don't use dnsmasq, I try the KEA route, as I have already configured it so far to my liking, so if possible, I will prefer not to switch. Also I would prefer not to go back to ISC, as I understand, this is end-of-life, so I don't want to use it anymore.
Also note that the IPs handed out by my ISP are technically not fixed ones. I have dynamic IPs, even though I notice that my IP has not changed since more than 2 years, but technically, I think it can any time, so for this reason my setup needs to be compatible with that and also the delegated prefixes.

[franco]

Should be this one:

# opnsense-patch https://github.com/opnsense/core/commit/c264c905


Cheers,
Franco

PS: you are right about the rest

[gstyle]

Hi everybody,

I will be in the same situation when I upgrade to 26.1 and honestly, I am somehow confused with the IPv6 topic.

I have a FTTH account with Telekom in Germany. I also get a /56 prefix.

My current setup:
KEA DHCP for IPv4. Different VLANs with different subnets.

For my VLAN interfaces and IPv6, I did the following:
- In the WAN interface I put "IPv6 Configuration Type: DHCPv6"
- In the LAN VLANS I put "IPv6 Configuration Type: Track interface"
 - Under "Track IPv6 Interface" I put my WAN interface and I assigned a unique prefix for each interface
- Under "Services" KEA DHCPv6 is disabled
- Under "Services" ISC DHCPv6 is enabled for the VLANs and shows the IP ranges
- "Service -> Router Advertisments" is set to "Assisted" for the single LAN VLANS.

DNSMasq is not enabled.

I have this IPv6 setup since the beginning and put it following a howto for my provider.

Will this still work with the 26.1 upgrade? (I think so with ISC running as a plugin...?)
More important: Is this the way to go? What would now be the recommended way for my setup?
- Different prefixes for my VLANS
- Dynamic IPv6 /56 prefix received from my provider when dialing in via PPPoE.

I think this will be relevant for a lot of users at least in Germany ;)


Cheers
Mario

[franco]

Again, nothing changes on the upgrade. We only added ways to get out of the historic automatic ISC-DHCPv6/Radvd integration which is also required to better configure Dnsmasq and Kea/Radvd IPv6 setups.


Cheers,
Franco