asconf: set last_control_chunk_from to null #661
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.
If we get ASCONF from a new address, i.e, we couldn't find the net,
set last_control_chunk_from to null. This will force ASCONF processing
to find the correct net later, else ASCONF_ACK ends up being sent
to the net where the last control chunk (like COOKIE_ECHO/COOKIE_ACK)
was received from.
Encountered this problem while working on https://datatracker.ietf.org/doc/draft-porfiri-tsvwg-sctp-natsupp/, where we want to send ASCONF from secondary addresses after a single homed session is setup.