Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-06-11 | Pass through unknown DUIDs (#71) | Michael Stapelberg | |
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. | |||
2018-05-06 | Added tests for OptClientId and using net.HardwareAddr for DUID (#58) | insomniac | |
2018-04-09 | add DUID-UUID (#32) | Pablo Mazzini | |
2018-03-06 | Fixed types in dhcpv4 and dhcpv6 | Andrea Barberio | |
2017-12-10 | Fixed DUID_LL handling | Andrea Barberio | |
2017-12-08 | Fixed DHCPv6Relay.Length() and added test | Andrea Barberio | |