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

Function to split Prefix to create multiple child prefixes #6731

New Issue
Closed
opened 2025-12-29 19:44:35 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:44:35 +01:00
Owner
Copy Link

Originally created by @chewborg on GitHub (Jul 28, 2022).

NetBox version

v3.2.2

Feature type

New functionality

Proposed functionality

I believe similar was close due to going stale, but previous request asked for additional functionality
3255

It would be useful to be able to split a Subnet Prefix into multiple child prefixes based on the logical division. This is something that I have found very useful and time saving in other IPAMs
For instance you have a /24 prefix as a Container, and you want to subdivide into 8 separate prefixes as /27 subnets
At present, as far as I can see, you must create a prefix for each one of the 8 in turn using the UI

Hoping this request is not replicated elsewhere.

Patrick

Use case

Reduces repetitive tasks for subdividing prefixes

Database changes

None required

External dependencies

No response

Originally created by @chewborg on GitHub (Jul 28, 2022). ### NetBox version v3.2.2 ### Feature type New functionality ### Proposed functionality I believe similar was close due to going stale, but previous request asked for additional functionality [3255](https://github.com/netbox-community/netbox/issues/3255) It would be useful to be able to split a Subnet Prefix into multiple child prefixes based on the logical division. This is something that I have found very useful and time saving in other IPAMs For instance you have a /24 prefix as a Container, and you want to subdivide into 8 separate prefixes as /27 subnets At present, as far as I can see, you must create a prefix for each one of the 8 in turn using the UI Hoping this request is not replicated elsewhere. Patrick ### Use case Reduces repetitive tasks for subdividing prefixes ### Database changes None required ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:44:35 +01:00
adam closed this issue 2025-12-29 19:44:35 +01:00
adam commented 2025-12-29 19:44:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 28, 2022):

Tagging this as relevant to (but not necessarily blocked by) #7845.

@jeremystretch commented on GitHub (Jul 28, 2022): Tagging this as relevant to (but not necessarily blocked by) #7845.
adam commented 2025-12-29 19:44:36 +01:00
Author
Owner
Copy Link

@elipsion commented on GitHub (Oct 20, 2022):

Isn't this more or less the "bulk create" function already implemented for IP addresses?
The only thing that's lacking is the intelligence (or a way to hint) for creating the correct step.

@elipsion commented on GitHub (Oct 20, 2022): Isn't this more or less the "bulk create" function already implemented for IP addresses? The only thing that's lacking is the intelligence (or a way to hint) for creating the correct [step](https://docs.python.org/3/library/stdtypes.html?highlight=range#range).
adam commented 2025-12-29 19:44:36 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 20, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 20, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:44:41 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 20, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 20, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner type: feature
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#6731
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?