issue creating a custom DHCPv4 option

[Stephen Morris]

On 17/02/13 17:28, Carsten Strotmann wrote:
> Hi,
> 
> I'm running in a similar issues with DHCPv6, where I try to define
> the option for RFC 6731: :


Carsten,

The problem that you can't create option with code '252' is caused by
the function that checks that you're not trying to override the
standard option's definition. Inadvertently the check for the range of
codes 224-254 (reserved for private use) was omitted: they are
therefore regarded as standard options and they can't be defined by a
user. This is a bug in the code and a ticket has been created for it:

http://bind10.isc.org/ticket/2772

The other issue is similar but there is slightly different reason for
it. We don't want users to redefine standard options so we check if
you're trying to create a definition of a standard option (option that
belongs to 'dhcp6' space and having a code reserved for standard
option) and reject that configuration. The function that performs this
check compares the option code against all codes registered by IANA:

http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml

while we still lack definitions of some of these options.

As a result, you can neither use the standard option for which we lack
the definition nor you can define it on your own because of the way we
check that you don't override the standard option's format.

We've created

http://bind10.isc.org/ticket/2773

... to supply the remaining definitions.  Once this is in place, you
will not have to add the definition of the option '74' to set its data.


Stephen and Marcin