restart DHCPv6 transaction on receival of RA who contains a new prefix #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When upstream DHCPv6 server does not provide IA_NA or IA_PD options, odhcp6c enters in stateless mode, which will not be exited from until SIGUSR2 signal is received.
This change enforce DHCPv6 transaction restart on receival of a RA that:
a) advertise the presence of DHCPv6 server in the network, either
by containing M or O flags
b) has a PI (prefix information) option that contains a new prefix
thus allowing the switch to DHCPv6 stateful mode when RA PI options suggest that upstream DHCPv6 server now manages a new prefix.
Transaction restart is useful even when DHCPv6 client is already in stateful mode, so DHCPv6 server will be able to refresh client's IA_NA and IA_PD options before renewal timeout is triggered, hence avoiding usage of potentially deprecated addresses.