From: Pasi Sjöholm <[email protected]> Patch1: The option length is always 0 if the rapid commit-option is included in the message. Instead of invalidating 0-lenght option, invalidate option lenght not being zero to make the rapid commit to work correctly. RFC3315, 22.14.
Patch2: If any error is got in the reply to rapid commit solicitation we need to fail and not to cause a loop of solicitation->reply->solicitation.. Patch3: Sometimes DHCPv6 server might not send any errors not being able to assign addresses. Eg. Cisco EPC3940L does not do so when IA_TA is requested at _advertise_ phase or later. Therefore it's possible to end up with request->reply->request... loop unless the requests are rate-limited. Not sure if samekind of fixes are needed for the rebind and renew. Pasi Sjöholm (3): gdhcp: Fix rapid commit option length check dhcpv6: Fail if we have error with rapid commit dhcpv6: Rate limit requests when no address is got gdhcp/client.c | 2 +- src/dhcpv6.c | 13 ++++++++++--- 2 files changed, 11 insertions(+), 4 deletions(-) -- 2.1.0 _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
