[kea-dev] RSOO bug in 0.9.1

Wlodek Wencel wlodek at isc.org
Mon Apr 13 15:07:57 UTC 2015

Thank you for your email. I checked again RSOO feature in Kea (sending
Vendor-Specific Information Option with multiple sub-options, what I
assume you do) and unfortunately I could not reproduce error you described.

Can you provide more details? Like kea config file and capture from
wireshark? Or details about Vendor-Specific Information Option you are
including to message?

Wlodek Wencel

On 04/11/2015 12:44 AM, Templin, Fred L wrote:
> Hello,
> I am trying to use the new RFC6422 Relay Supplied Options Option (RSOO) facility.
> My RFC6221 relay inserts a Vendor-Specific Information Option (option #17) in the
> Relay-forward message that will be sent to the kea server. The option has length
> 26 decimal. But, when the kea server does the RFC6422 transformation it truncates
> the VSIO to only include the option header and the 4-byte enterprise number. The
> VSIO is then inserted into the DHCPv6 Reply message, but loses the 22 bytes that
> follow the enterprise number.
> See attached for the kea log. It does not show anything about the Relay-forward
> or Relay-reply messages, but does show how the server inserts the VSIO with
> length 4. Please let me know if any further information is needed.
> Fred Templin
> _______________________________________________
> kea-dev mailing list
> kea-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-dev

More information about the kea-dev mailing list