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

Associate IPv4 and IPv6 Prefix With #9556

New Issue
Closed
opened 2025-12-29 21:18:56 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:18:56 +01:00
Owner
Copy Link

Originally created by @emallette on GitHub (Apr 29, 2024).

NetBox version

v3.7.6

Feature type

New functionality

Proposed functionality

What I propose are two pieces:

  1. extend the Prefix Model to include the Circuit-ID, so you can associate a given prefix with a Circuit ID. As an aside, I can already do this today with a Custom Field.

The second piece I was not able to accomplish within the existing UI.
2) I would then propose for a given circuit that it would display all IP prefixes that match %circuit-ID% within the circuit-ID display.
-- It would also be nice if IP Prefix would show up as a an option in Configure Table for the Circuit Summary page.

Use case

It allows operators to easily see what IPv4 and IPv6 prefixes are assigned to a given customer circuit - this could be more than one prefix per family.

Database changes

It does require a new field Circuit > Circuit in the Prefix Model, though that field already exists in the Circuit Model.

External dependencies

I do not believe it would require any external dependencies.

Originally created by @emallette on GitHub (Apr 29, 2024). ### NetBox version v3.7.6 ### Feature type New functionality ### Proposed functionality What I propose are two pieces: 1) extend the Prefix Model to include the Circuit-ID, so you can associate a given prefix with a Circuit ID. As an aside, I can already do this today with a Custom Field. The second piece I was not able to accomplish within the existing UI. 2) I would then propose for a given circuit that it would display all IP prefixes that match %circuit-ID% within the circuit-ID display. -- It would also be nice if IP Prefix would show up as a an option in Configure Table for the Circuit Summary page. ### Use case It allows operators to easily see what IPv4 and IPv6 prefixes are assigned to a given customer circuit - this could be more than one prefix per family. ### Database changes It does require a new field Circuit > Circuit in the Prefix Model, though that field already exists in the Circuit Model. ### External dependencies I do not believe it would require any external dependencies.
adam added the type: feature label 2025-12-29 21:18:56 +01:00
adam closed this issue 2025-12-29 21:18:56 +01:00
adam commented 2025-12-29 21:18:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 29, 2024):

extend the Prefix Model to include the Circuit-ID, so you can associate a given prefix with a Circuit ID.

This would not make sense to implement natively as there is no direct relationship between a prefix an a circuit ID. As you note, it can be accomplished by using a custom field if needed.

I would then propose for a given circuit that it would display all IP prefixes that match %circuit-ID% within the circuit-ID display.

This would be a very niche piece of functionality that likewise would not be appropriate to implement in core. However, you can likely accomplish what you're after by writing a custom plugin.

@jeremystretch commented on GitHub (Apr 29, 2024): > extend the Prefix Model to include the Circuit-ID, so you can associate a given prefix with a Circuit ID. This would not make sense to implement natively as there is no direct relationship between a prefix an a circuit ID. As you note, it can be accomplished by using a custom field if needed. > I would then propose for a given circuit that it would display all IP prefixes that match %circuit-ID% within the circuit-ID display. This would be a very niche piece of functionality that likewise would not be appropriate to implement in core. However, you can likely accomplish what you're after by writing a [custom plugin](https://docs.netbox.dev/en/stable/plugins/).
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 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#9556
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?