Project

General

Profile

Feature #3029

DHCPv6 Server/RA page should list interfaces that are configured to track DHCP-PD

Added by Daniel Becker almost 6 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
DHCP6
Target version:
Start date:
06/06/2013
Due date:
% Done:

100%

Estimated time:

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.

Associated revisions

Revision 2bf455ca (diff)
Added by Renato Botelho about 3 years ago

Ticket #3029

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

Revision a3d07046 (diff)
Added by Renato Botelho about 3 years ago

Ticket #3029

Teach merge_ipv6_delegated_prefix() to deal with other PD sizes

Revision 15db02a6 (diff)
Added by Renato Botelho about 3 years ago

Ticket #3029

Teach services_dhcpdv6_configure() to deal with PD length != 64

Revision 6c8beed3 (diff)
Added by Renato Botelho about 3 years ago

Ticket #3029

Fix DHCPv6 GUI to work with PD length != 64

Revision ada3eeb3 (diff)
Added by Renato Botelho about 3 years ago

Fix #3029

Teach system_hosts_generate() to deal with PD length != 64

Revision 7a9f8774 (diff)
Added by Chris Buechler about 3 years ago

Simplify check for which interfaces can have RAs, and show track6 interfaces without having to enable DHCPv6 server. Ticket #3029

Revision e1953efa (diff)
Added by Chris Buechler about 3 years ago

DHCPv6 clean ups for PD. Ticket #3029

Revision 7c4c43a5 (diff)
Added by Chris Buechler about 3 years ago

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

Revision 8e187daa (diff)
Added by Chris Buechler about 3 years ago

Allow disabling of radvd with track6 interfaces. Ticket #3029

Revision 430d7e93 (diff)
Added by Chris Buechler about 3 years ago

Only enable DHCPv6 server for track6 interfaces where it's enabled. Ticket #3029

Revision 830ea39a (diff)
Added by Chris Buechler about 3 years ago

Skip configuring dhcpdv6 when the interface doesn't have a valid subnet (like track6 where PD hasn't been obtained). Ticket #3029

Revision 5d314c0a (diff)
Added by Chris Buechler about 3 years ago

Fix DHCPv6 server check to allow track6. Ticket #3029

Revision b5fcc2b5 (diff)
Added by Chris Buechler about 3 years ago

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

Revision a5776226 (diff)
Added by Chris Buechler about 3 years ago

A PD-obtained subnet is always a /64 on the interface, so should be shown as such here in DHCPv6 server. Ticket #3029

History

#1 Updated by Daniel Becker almost 5 years ago

Could somebody comment whether this is an intentional restriction, or just something nobody got around to implementing?

#2 Updated by Cino . almost 5 years ago

Can this be changed to a Bug instead of a feature request?

#3 Updated by Michael Virgilio over 4 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.

#4 Updated by Adrien Carlyle about 4 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.

#5 Updated by Robert Nelson almost 4 years ago

I've add PR # 1638 to fix this issue.

#6 Updated by Anonymous over 3 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.

#7 Updated by Robert Stevens over 3 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.

#8 Updated by Michael Virgilio over 3 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

#9 Updated by Anonymous over 3 years ago

That is great to hear. Thank you. I'll keep an eye out.

#10 Updated by Jim Thompson over 3 years ago

  • Assignee set to Chris Buechler
  • Target version set to 2.3

#11 Updated by Jim Thompson about 3 years ago

  • Assignee changed from Chris Buechler to Renato Botelho

#12 Updated by Jim Thompson about 3 years ago

  • Status changed from New to Assigned

#13 Updated by Renato Botelho about 3 years ago

  • Status changed from Assigned to Feedback
  • % Done changed from 0 to 100

#14 Updated by Michael Virgilio about 3 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 3 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 3 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.

Also available in: Atom PDF