Updating MPTCP configurations to integrate with SLAAC #471
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Monika-Research <monika.prakash@tii.ae>
Monika-Research
assigned joenpera, saauvine, mbaddeley and Monika-Research and unassigned mbaddeley, joenpera and saauvine
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
MPTCP configurations are changed inorder to use SLAAC IPv6 addresses.
Note: S90mptcp service is called only after checking if the interfaces are up in entrypoint_nats.sh. As the radios are not brought up at entrypoint_nats.sh, S90mptcp service is not run by default. As there is no recent plan of having MPTCP in meshshield, S90mptcp service is called manually for testing purpose.