diff options
| author | Michael Stapelberg <stapelberg@users.noreply.github.com> | 2018-06-11 14:15:37 +0200 |
|---|---|---|
| committer | insomniac <insomniacslk@users.noreply.github.com> | 2018-06-11 13:15:37 +0100 |
| commit | 5be287562fa0c968908d8d908cb695db880dfec4 (patch) | |
| tree | 63d2907a107aea720817553a75e70ca3c26fbb7d /dhcpv6/option_relaymsg_test.go | |
| parent | 5717652a33b34ce6ee9a9e89602b4eb323cea4af (diff) | |
Pass through unknown DUIDs (#71)
I’m building on a program which works with user-supplied DUIDs. Before this
change, the code would panic when users provide a DUID which is not (yet)
implemented.
In addition to this being a better failure mode, the behavior is also mandated
by the DHCPv6 RFC: https://tools.ietf.org/html/rfc3315#section-9 states:
Clients and servers MUST treat DUIDs as opaque values and MUST only
compare DUIDs for equality.
Diffstat (limited to 'dhcpv6/option_relaymsg_test.go')
0 files changed, 0 insertions, 0 deletions