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

Circuit and related prefixes view #1641

New Issue
Closed
opened 2025-12-29 16:33:44 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:33:44 +01:00
Owner
Copy Link

Originally created by @PeepOks on GitHub (Mar 23, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.5
  • NetBox version: 2.3.1

Description

We would like to view what network prefixes are provided by what circuit. This info would help us to find Provider/ISP more quickly when it is needed. Some Circuits can have many prefixes related to them
I don't know if this is supported by a current database schema.

Originally created by @PeepOks on GitHub (Mar 23, 2018). ### Issue type [x] Feature request [ ] Bug report [ ] Documentation ### Environment * Python version: 2.7.5 * NetBox version: 2.3.1 ### Description We would like to view what network prefixes are provided by what circuit. This info would help us to find Provider/ISP more quickly when it is needed. Some Circuits can have many prefixes related to them I don't know if this is supported by a current database schema.
adam closed this issue 2025-12-29 16:33:44 +01:00
adam commented 2025-12-29 16:33:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 29, 2018):

Thank you for your interest in NetBox. It looks like your feature request is missing some information. Per the contributing guidelines, please ensure that you have provided all of the following:

  • A detailed description of the proposed functionality
  • A use case for the feature; who would use it and what value it would add to NetBox
  • A rough description of changes necessary to the database schema (if applicable)
  • Any third-party libraries or other resources which would be involved

Please update the issue so that it meets all of these requirements. If no response is received within a week, this issue will be closed. Thanks!

@jeremystretch commented on GitHub (Mar 29, 2018): Thank you for your interest in NetBox. It looks like your feature request is missing some information. Per the [contributing guidelines](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md), please ensure that you have provided all of the following: * A detailed description of the proposed functionality * A use case for the feature; who would use it and what value it would add to NetBox * A rough description of changes necessary to the database schema (if applicable) * Any third-party libraries or other resources which would be involved Please update the issue so that it meets all of these requirements. If no response is received within a week, this issue will be closed. Thanks!
adam commented 2025-12-29 16:33:45 +01:00
Author
Owner
Copy Link

@PeepOks commented on GitHub (Apr 5, 2018):

We have many circuits where ISP provides us multiple L2 uplinks and we have 2 routers(for redundancy) what use same circuit. I have a problem when I want to add both routers uplinks to circuit. In circuit configuration only one A side termination is allowed.
Current solution works best if ISP provides L3 uplinks.

If circuit and network prefix relation would exist then we can know what circuit or ISP provides us specific public network prefix.

@PeepOks commented on GitHub (Apr 5, 2018): We have many circuits where ISP provides us multiple L2 uplinks and we have 2 routers(for redundancy) what use same circuit. I have a problem when I want to add both routers uplinks to circuit. In circuit configuration only one A side termination is allowed. Current solution works best if ISP provides L3 uplinks. If circuit and network prefix relation would exist then we can know what circuit or ISP provides us specific public network prefix.
adam commented 2025-12-29 16:33:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

Circuits can be terminated to interfaces, and IP addresses can be assigned to interfaces. You'll need to create a separate circuit in NetBox for each router.

@jeremystretch commented on GitHub (Jul 18, 2018): Circuits can be terminated to interfaces, and IP addresses can be assigned to interfaces. You'll need to create a separate circuit in NetBox for each router.
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
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#1641
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?