Project

General

Profile

Actions

Feature #3971

closed

IPv6 - Preserve the DUID used for WAN DHCP-PD in the configuration file

Added by David Williams over 9 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
Start date:
11/01/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Feature Request

Preserve the DUID used to obtain the DHCP-PD addressing on the WAN in config.xml

Secondary request to then make this editable in webConfigurator.

Justification and Use Case

When you reinstall or move to new hardware, a new DUID is generated. This results in new IPv6 address space being assigned by the service provider. If you have been assigned a /56 or /60 and used the networks for manual assignment in OpenVPN or firewall rules for example, then you need to touch all those configurations and make the changes to the new networks.

If the DUID was maintained in config.xml, then you would be able to get the same address space back after re-imaging or moving to new hardware, upon restoring the configuration.

--

Secondary, the DUID in config.xml should then be user editable in the GUI. Use case ... If you initially set the WAN DHCP-PD prefix length to the default /64 then decide you need a /60, it creates problems because the service provider (Comcast) will keep issuing a /64 based on the DUID and not flip the DHCP-PD lease to a /60 automatically on the next request. If the DUID was user editable, then it could be changed on-demand and the provider would see you as a new device and instantly assign a different DHCP-PD lease.

Actions #1

Updated by Landon Timothy about 8 years ago

Any chance part one could be looked into for 2.3?
Would be nice to preserve this when reinstalling or moving hardware.
If not, how can this be accomplished manually?

Actions #2

Updated by Chris Buechler about 8 years ago

  • Category set to Interfaces
Actions #3

Updated by Jim Pingle over 7 years ago

As mentioned in #6667, this also negatively impacts those with /var in RAM

Actions #4

Updated by Martin Wasley over 7 years ago

Added as part of PR #3262

Actions #5

Updated by Kill Bill over 6 years ago

Actions #6

Updated by Jim Pingle over 6 years ago

  • Status changed from New to Resolved
  • Target version changed from Future to 2.4.0
Actions

Also available in: Atom PDF