Skip to content

[NUT] Support custom subnet length and /31 and /127 subnet in IP allocation.#23638

Open
netobani wants to merge 1 commit intosonic-net:masterfrom
netobani:user/r12f/nut-subnet-rebased
Open

[NUT] Support custom subnet length and /31 and /127 subnet in IP allocation.#23638
netobani wants to merge 1 commit intosonic-net:masterfrom
netobani:user/r12f/nut-subnet-rebased

Conversation

@netobani
Copy link
Copy Markdown
Contributor

@netobani netobani commented Apr 4, 2026

Description of PR

Summary:
Rebased from #22122. Support custom subnet length handling, including /31 and /127 subnet allocation in NUT IP allocation.

Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Approach

What is the motivation for this PR?

Rebased from #22122. NUT IP allocation needs to support custom subnet lengths, including /31 and /127 subnets.

How did you do it?

Updated the NUT IP allocation logic in ansible/library/nut_allocate_ip.py to support custom subnet length handling and correctly process /31 and /127 subnets.

How did you verify/test it?

Not run in this rebase-only task.

Any platform specific information?

N/A

Supported testbed topology if it's a new test case?

N/A

Documentation

N/A

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@github-actions github-actions bot requested review from r12f, wangxin and xwjiang-ms April 4, 2026 04:41
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants