Re: [Kea-users] How to define "code width" / "length width" on Vendor-Specific Information option (code 43)

2021-04-29 Thread Kotetsu kakko
Thank you for your answer! I think Kea's implementation is correct, and the client implementation should be fixed. Regards. 2021年4月24日(土) 4:35 Francis Dupont : > You can't: Kea wires these widths to the DHCP version (one octet for v4 > and two for v6). You have to use the binary format or to wr

Re: [Kea-users] How to define "code width" / "length width" on Vendor-Specific Information option (code 43)

2021-04-23 Thread Francis Dupont
You can't: Kea wires these widths to the DHCP version (one octet for v4 and two for v6). You have to use the binary format or to write a hook converting the option content. BTW if the RFC 2132 loosely specifies the option 43 there is a SHOULD about the suboption format which clearly does not allow

[Kea-users] How to define "code width" / "length width" on Vendor-Specific Information option (code 43)

2021-04-23 Thread Kotetsu kakko
Hi! I want to convert isc-dhcp-server config below to Kea. ``` option space test_opt code width 2 length width 2 hash size 17; option test_opt.script-url code 36 = text; subnet 10.138.127.128 netmask 255.255.255.128 { option routers 10.138.127.129; option subnet-mask 255.255.255.128; range d