DHCPv6 Server/RA page should list interfaces that are configured to track DHCP-PD
The configuration page for the DHCPv6 server and router advertisements currently only lists those interfaces that have a static IPv6 address assigned; however, given that both DHCPv6 and router advertisements are automatically enabled for DHCP-PD target interfaces as well (with some of the values automatically determined), it would make sense to include such interfaces in that page.
Import patch from @Robert-Nelson to enable DHCPv6 Server/RA to
interfaces configured to track DHCP-PD
This patch only works for PD with length 64
Teach merge_ipv6_delegated_prefix() to deal with other PD sizes
Teach services_dhcpdv6_configure() to deal with PD length != 64
Simplify check for which interfaces can have RAs, and show track6 interfaces without having to enable DHCPv6 server. Ticket #3029
Add config upgrade code to enable and configure DHCPv6 server and radvd where track6 is in use, as they were automatically configured previously. Add same config to default config.xml to retain existing behavior there. Ticket #3029
Only enable DHCPv6 server for track6 interfaces where it's enabled. Ticket #3029
Skip configuring dhcpdv6 when the interface doesn't have a valid subnet (like track6 where PD hasn't been obtained). Ticket #3029
Remove the code block to "fake" DHCPv6 server, now that it's unnecessary. Ticket #3029
also ref: https://forum.pfsense.org/index.php?topic=107537.msg600111#msg600111
#4 Updated by Adrien Carlyle about 5 years ago
Would like to see this added to the product. I currently require the use of DHCPv6/RA so that I can use IPv6 on my LAN complete with name resolution but have hit a snag in 2.2.1 because of https://redmine.pfsense.org/issues/4436.
I've worked around this using the following forum post:
Ideally I'd like to use the track interface option. However, that currently means I have to drop DHCPv6 for roughly half of the clients on my network entirely because they do not support SLAAC. Name resolution also becomes problematic.
#8 Updated by Michael Virgilio about 4 years ago
Don, in the forums one of the developers has said that the ability to adjust DHCPv6 and RA settings for interfaces using "Track Interface" should be available in pfSense 2.3. It's not there yet, so don't go rushing out to download it, especially since it's just reached beta.
#14 Updated by Michael Virgilio about 4 years ago
AWESOME to see this finally in pfSense!!! A few things I've noticed just from my quick use of it...
- If the "Enable DHCPv6 Server" box is checked on first visit to the DHCPv6 Server page, when unchecked, the settings remain visible. Then re-checking the box, the settings disappear.
- RA settings don't appear until DHCPv6 server is enabled. But RA settings could be set such that DHCPv6 isn't used (i.e. Router Only or Unmanaged). As a result, shouldn't the RA settings always be available? Maybe make the RA settings the first page, then depending on what the Router Mode setting is set to, determine whether or not to allow enabling the DHCPv6 server?
- Since RA settings should be able to be made regardless of DHCPv6 server settings, the checkbox under DNS Configuration to use the same settings as DHCPv6 server should be disabled (or hidden?) if DHCPv6 server is disabled.
#15 Updated by Chris Buechler about 4 years ago
Cleaned up a lot of this. DHCPv6 server and radvd can now be disabled with track6. Interfaces that haven't gotten a PD omitted from dhcpdv6.conf rather than making it throw errors. Fixed RA page when DHCPv6 server isn't enabled.
Enable checkbox issue is unrelated to this, opened #5914 for that.
I think that should cover everything for subject feature.
#16 Updated by Chris Buechler about 4 years ago
- Status changed from Feedback to Resolved
This all works correctly now. The range and static mappings are supported.
prefix6 support for PD of PD-obtained subnets isn't supported. That's complicated for the reasons discussed in this thread.
That's something we can look at in the future. Opened feature #5950 to cover that.