Feature #3029
closed
DHCPv6 Server/RA page should list interfaces that are configured to track DHCP-PD
Added by Daniel Becker over 11 years ago. Updated over 8 years ago.
100%
Description
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.
Updated by Daniel Becker over 10 years ago
Could somebody comment whether this is an intentional restriction, or just something nobody got around to implementing?
Updated by Cino . over 10 years ago
Can this be changed to a Bug instead of a feature request?
Updated by Anonymous almost 10 years ago
Definitely interested in this one. Other open source router firmwares have figured out how to do DHCPv6 on a LAN that has a PD prefix... surely it can be done here too.
Updated by Adrien Carlyle over 9 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:
https://forum.pfsense.org/index.php?topic=90699.msg502875#msg502875
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.
Updated by
Updated by Anonymous almost 9 years ago
Any movement on this at all? I have yet to find a easy way to use my own DNS server internally with a prefix provided to me by comcast while using track interface.
Updated by Robert Stevens almost 9 years ago
@Don, I also have ran into the same stumbling block as you. Every comcast customer using pfsense is also thinking the same thing. The lack of this feature is really frustrating when pfsense is powerful in almost everything else that it does.
Updated by Anonymous almost 9 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.
Reference: https://forum.pfsense.org/index.php?topic=97168.msg541632#msg541632
Updated by Anonymous almost 9 years ago
That is great to hear. Thank you. I'll keep an eye out.
Updated by Jim Thompson almost 9 years ago
- Assignee set to Chris Buechler
- Target version set to 2.3
please also check https://github.com/pfsense/pfsense/pull/1638
Updated by Jim Thompson almost 9 years ago
- Assignee changed from Chris Buechler to Renato Botelho
Updated by Renato Botelho almost 9 years ago
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
Applied in changeset ada3eeb33cadce1c05b67462c03bb51d6646cba2.
Updated by Anonymous almost 9 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.
Updated by Chris Buechler almost 9 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.
Updated by Chris Buechler over 8 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.
https://forum.pfsense.org/index.php?topic=107537.msg600423#msg600423
That's something we can look at in the future. Opened feature #5950 to cover that.