starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

[PR #3396] [CLOSED] Added support for /32 and /128 prefixes #12554

New Issue
Closed
opened 2025-12-29 22:22:14 +01:00 by adam · 0 comments
adam commented 2025-12-29 22:22:14 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/3396
Author: @SimonGurney
Created: 8/6/2019
Status: ❌ Closed

Base: develop ← Head: develop

📝 Commits (1)

  • 219d242 Added support for /32 and /128 prefixes

📊 Changes

3 files changed (+9 additions, -13 deletions)

View changed files

📝 .gitignore (+2 -0)
📝 netbox/ipam/models.py (+6 -12)
📝 netbox/ipam/views.py (+1 -1)

📄 Description

Fixes:

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/3396 **Author:** [@SimonGurney](https://github.com/SimonGurney) **Created:** 8/6/2019 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `develop` --- ### 📝 Commits (1) - [`219d242`](https://github.com/netbox-community/netbox/commit/219d24274ffb3bdd7387252559a32e49470fbb3c) Added support for /32 and /128 prefixes ### 📊 Changes **3 files changed** (+9 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `.gitignore` (+2 -0) 📝 `netbox/ipam/models.py` (+6 -12) 📝 `netbox/ipam/views.py` (+1 -1) </details> ### 📄 Description <!-- Thank you for your interest in contributing to NetBox! Please note that our contribution policy requires that a feature request or bug report be opened for approval prior to filing a pull request. This helps avoid wasting time and effort on something that we might not be able to accept. Please indicate the relevant feature request or bug report below. IF YOUR PULL REQUEST DOES NOT REFERENCE AN ACCEPTED BUG REPORT OR FEATURE REQUEST, IT WILL BE MARKED AS INVALID AND CLOSED. --> ### Fixes: <!-- As an ISP, we routinely have to allocate /32 and /128 prefixes as framed routes for our clients on DSL, VDSL connectivity etc. To do this we pro-grammatically, we need to be able to request /32 prefixes via the API. Looking through the issue log, I see this has been discussed before but /32 is not considered a prefix but rather an address. I would argue this isn't the case as framed routes make use of /32 prefixes as do loopback allocations. We allocate /32 prefixes from our address pools, alongside larger prefixes. Without this modification we have two issues preventing us from using netbox: 1. We would have to arbitrarily carve out blocks of our public address space for sole use as /32's and then request these allocations as IP addresses. This makes it confusing to see overall allocation in the UI. 2. We cannot port our existing allocations into netbox from our existing IPAM product and therefore have to run the two product in parallel. I hope you can see that /32 prefixes do have a place and approve this pull request as otherwise you are excluding organisations from using this brilliant product. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 22:22:14 +01:00
adam closed this issue 2025-12-29 22:22:14 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#12554
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?