[FS#1462] odhcp6c fails to renew and rebind addresses
LEDE Bugs
lede-bugs at lists.infradead.org
Wed Apr 4 01:09:14 PDT 2018
The following task has a new comment added:
FS#1462 - odhcp6c fails to renew and rebind addresses
User who did this - Clemens Fruhwirth (clefru)
----------
Thanks Hans for your feedback, and looking through my trace!
Would you consider this trunked upstream reply an RFC violation? From [[http://https://tools.ietf.org/html/rfc3633#page-15|RFC 3633]] 12.2:
" The delegating router MUST include an IA_PD Prefix option or options
(in an IA_PD option) in Reply messages sent to a requesting router."
This does not seem to fulfilled by the delegating router as zero IA_PD Prefix options are included with the IA_PD option. I will contact my ISP about that.
However, that doesn't mean that T1=T2s are inappropriately set in the reply, because in the RFC right above the quoted section we also have: "the delegating router MAY send a Reply message to the requesting router containing the IA_PD with the lifetimes of the prefixes in the IA_PD set to zero". From that I read that REBIND replies with IA_PD having T1=T2=0 are valid.
This case isn't handled so well by odhcp6c as it will loop in REBIND forever. Shouldn't it go back to Solicitation eventually?
Sidenote: Your suggested "set defaultsreqopts 0" trick did not work for me although my odhpc6 gets correctly launched with the "-R" flag. Reason being my upstream DHCP server sets the unicast option, even when not requested in the reply and odhcp6c happily parses and accepts it. As I have now set up a build environment for odhcp6c now, I just removed the unicast flag handling from my binary.
----------
More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1462#comment4553
More information about the lede-bugs
mailing list