[NUT] Support custom subnet length and /31 and /127 subnet in IP allocation.#22122
Closed
r12f wants to merge 1 commit intosonic-net:masterfrom
Closed
[NUT] Support custom subnet length and /31 and /127 subnet in IP allocation.#22122r12f wants to merge 1 commit intosonic-net:masterfrom
r12f wants to merge 1 commit intosonic-net:masterfrom
Conversation
Signed-off-by: r12f <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
force-pushed
the
user/r12f/nut-subnet
branch
from
141ee20 to
8b0b053
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
12 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Sometimes we need different P2P IP range than /30 and /126. And when /31 and /127 subnet is being used, we cannot take the second and third IPs anymore.
How did you do it?
This change add support to subnet length as well as supporting /31 and /127 by using the first and second IPs when these subnets are used.
How did you verify/test it?
Run locally and working fine.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation