[Dibbler] Question: Does DHCP Server supoports "Prefix Delegation reconfiguration"
michaelx.rapoport at intel.com
Sun Mar 31 09:03:45 CEST 2013
Thank you for clarification.
My concern comes from the following requirement of the attached document:
"If the eRouter has used all of its sub-prefixes and new Customer-Facing Logical Interfaces are enabled, the eRouter MUST revoke the most recently delegated sub-prefix and use it to assign /64 interface-prefixes to the new Customer-Facing Logical Interface(s). If more /64 interface-prefixes are needed, the eRouter MUST continue to revoke delegated sub-prefixes from most recent to least recent until all Customer-Facing Logical Interfaces have been assigned /64 interface-prefixes."
According to this requirement there is a need to revoke the previously delegated Prefix, possibly by using the Release command and configure the interfaces.
Is it possible to cause Dibbler sending the Release command ?
From: dibbler-bounces at klub.com.pl [mailto:dibbler-bounces at klub.com.pl] On Behalf Of thomson
Sent: Saturday, March 30, 2013 20:56
To: Dibbler users list
Subject: Re: [Dibbler] Question: Does DHCP Server supoports "Prefix Delegation reconfiguration"
On Wed, 27 Mar 2013 10:32:49 +0000, "Rapoport, MichaelX"
<michaelx.rapoport at intel.com> wrote:
> Does the DHCP Server supports the "Prefix Delegation reconfiguration"
> as defined in RFC 3633, p. 13 ?
Reconfigure is not yet officially supported. There's reconfigure branch in git, but it is a work in progress. It may or may not work. Keep in mind that reconfigure is a much more broader functionality that is not specific to PD and covers all other aspects of the client (or delegating router). You may try this code from branch, but don't be disappointed if it does not work for you.
> How can I revoke the Delegated Prefix ?
Start the server, have it delegate a prefix to your device. Stop the server and configure it to no longer assign prefixes (e.g. comment out pd-class).
When requesting router renews, server will not renew its prefixes.
On a somewhat related note, I've made some progress on CONFIRM support on server side. Previously server didn't have enough information about the network to respond to CONFIRMs, so I added a new parameter called subnet.
It is now possible to specify which subnet is valid on a given interface.
It is not usable for you yet, as server uses this information for selecting relays, but not to respond to CONFIRMs yet. But it is likely that I'll implement this fix sometime next week. This will address bugs #240 and #259.
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 939176 bytes
More information about the Dibbler