Problems setting up dhcpv6 option 59 (boot file name -- rfc5970) on bind10

[Marcin Siodelski]

Angelo,

Many thanks for your email. Currently dhcp server provides a limited set of std option definitions. The option 59 doesn't have its definition in src/lib/dhcp/std_option_defs.h, and that's why the configuration mechanism complains. On the other hand, there is a function in libdhcp++ which you probably spotted already, that checks whether the given option is a standard option or custom one. It does it to make sure that nobody overrides the format of a standard option, which doesn't make much sense, but may rather cause trouble.

However, this check shouldn't be so strict as long as we don't have definitions for all standard options as it causes grief for someone trying to setup the value for such an option.

If you have an account on bind10.isc.org, can you please submit a bug ticket for your problem? Please assign it to DHCP sub-project and libdhcp component. If you don't have an account, please let me know. I will file a bug on my own.

Thanks for your efforts and reporting this problem.

Marcin



----- Original Message -----
> From: "Angelo Failla" <pallotron at fb.com>
> To: "Angelo Failla" <pallotron at fb.com>, bind10-dhcp at lists.isc.org
> Sent: Tuesday, January 28, 2014 6:40:22 PM
> Subject: Re: Problems setting up dhcpv6 option 59 (boot file name --	rfc5970) on bind10
> 
> It looks like you treat everything < 79 like standard option in
> src/lib/dhcp/libdhcp++.cc
> --
> Angelo Failla
> 
> Site Reliability Operations Dublin
> Pallotron at fb.com
> 
> 
> 
> 
> On 1/28/14, 9:33 AM, "Angelo Failla" <pallotron at fb.com> wrote:
> 
> >Hi,
> >
> >I¹m testing bind10 dhcpv6 and I¹m having troubles setting up option 59.
> >
> >Here is my config:
> >
> >> config show_json Dhcp6/
> >{"option-data": [{"data": "n", "code": 144, "space": "dhcp6",
> >"csv-format": true, "name": "tmpfs"}, {"data": "2401:db00:eef0:a52::,
> >2401:db00:eef0:b52::", "code": 23, "space": "dhcp6", "csv-format": true,
> >"name": "dns-servers"}, {"data":
> >"tftp://[fe80::202:c9ff:feca:f56a]:69/efi/efidefault", "code": 59,
> >"space": "dhcp6", "name": "boot-file-name", "csv-format": true}],
> >"option-def": [{"code": 144, "type": "string", "record-types": "",
> >"encapsulate": "", "space": "dhcp6", "array": false, "name": "tmpfs"}]}
> >
> >
> >
> >When running config commit I get this:
> >
> >> config commit
> >Error: Configuration parsing failed: the CSV option data format can be
> >used to specify values for an option that has a definition. The option
> >with code 59 does not have a definition.
> >Configuration not committed
> >
> >
> >
> >I tried to define option 59 like this:
> >
> >> config set Dhcp6/option-def[1]/name "boot-file-name"
> >> config set Dhcp6/option-def[1]/code 59
> >> config set Dhcp6/option-def[1]/type string
> >> config set Dhcp6/option-def[1]/array false
> >> config set Dhcp6/option-def[1]/record-types ""
> >> config set Dhcp6/option-def[1]/space "dhcp6"
> >> config set Dhcp6/option-def[1]/encapsulate ""
> >
> >But I get this error when committingŠ
> >
> >> config commit
> >Error: Configuration parsing failed: unable to override definition of
> >option '59' in standard option space 'dhcp6'.
> >Configuration not committed
> >
> >Any idea of what I¹m doing wrong? I guess the server treats option 59 as a
> >standard v6 option but I can¹t find any reference of it in the html guide
> >(http://bind10.isc.org/docs/bind10-guide.html#dhcp6-std-options-list)
> >
> >I¹m running 1.1.0 (the stable version =>
> >ftp://ftp.isc.org/isc/bind10/1.1.0/)
> >
> >
> >--
> >Angelo Failla
> >
> >Site Reliability Operations Dublin
> >Pallotron at fb.com
> >
> >
> >_______________________________________________
> >bind10-dhcp mailing list
> >bind10-dhcp at lists.isc.org
> >https://lists.isc.org/mailman/listinfo/bind10-dhcp
> 
> _______________________________________________
> bind10-dhcp mailing list
> bind10-dhcp at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind10-dhcp
>