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

Show ASNs per RIR #5993

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

Originally created by @ryanmerolle on GitHub (Jan 24, 2022).

NetBox version

v3.1.6

Feature type

New functionality

Proposed functionality

Currently the page for a RIR record only shows the associated aggregates, and it only has a button to add an aggregate.

With ASNs needing to be associated to a RIR, the RIR object view should be updated accordingly.

Use case

Enable consistency with regards to object pages in the GUI.

Database changes

N/A

External dependencies

N/A

Originally created by @ryanmerolle on GitHub (Jan 24, 2022). ### NetBox version v3.1.6 ### Feature type New functionality ### Proposed functionality Currently the page for a RIR record only shows the associated aggregates, and it only has a button to add an aggregate. With ASNs needing to be associated to a RIR, the RIR object view should be updated accordingly. ### Use case Enable consistency with regards to object pages in the GUI. ### Database changes N/A ### External dependencies N/A
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:35:28 +01:00
adam closed this issue 2025-12-29 19:35:28 +01:00
adam commented 2025-12-29 19:35:28 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Jan 24, 2022):

Maybe an idea to introduce LIRs on top of the RIR?
LIRs own address space and ASN's.

The RIR object has always confused me. There are only 5 RIRs, so why make them dynamic?

Currently I use a RIR rather as a LIR.
A LIR would model the IP world better, because it is the glue between public ASN and the prefixes.

P

@PieterL75 commented on GitHub (Jan 24, 2022): Maybe an idea to introduce LIRs on top of the RIR? LIRs own address space and ASN's. The RIR object has always confused me. There are only 5 RIRs, so why make them dynamic? Currently I use a RIR rather as a LIR. A LIR would model the IP world better, because it is the glue between public ASN and the prefixes. P
adam commented 2025-12-29 19:35:28 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jan 24, 2022):

That sounds like a feature request to create a way to model LIR membership. I get your thinking and confusion, but it likely is a low return and high investment feature request. It can be useful for modeling when there is some reason a company manages multiple LIRs (maybe an MSP with tenants, or a firm that went through some mergers and acquisitions).

This feature request was just to enable some assumed functionality within the NetBox views given this view is in place for most other objects with similar relationship models.

@ryanmerolle commented on GitHub (Jan 24, 2022): That sounds like a feature request to create a way to model LIR membership. I get your thinking and confusion, but it likely is a low return and high investment feature request. It can be useful for modeling when there is some reason a company manages multiple LIRs (maybe an MSP with tenants, or a firm that went through some mergers and acquisitions). This feature request was just to enable some assumed functionality within the NetBox views given this view is in place for most other objects with similar relationship models.
adam commented 2025-12-29 19:35:28 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 24, 2022):

LIRs own address space and ASN's.

At least in North America, ASN's are only owned and managed by the RIR. LIR's do not handle ASNs. LIR's only handle allocations for sub-delegation. I don't think this relationship needs a model, as in most cases LIR's could be modelled by a "tenant" on a prefix.

It looks like, at least for ASN's, APNIC, RIPE, LACNIC, and AFNIC are all the same

Prefixes could be modelled differently, but it looks like at least a few use the RIR > NIC > LIR. I think it is easier to just model RIR.

With ASNs needing to be associated to a RIR, the RIR object view should be updated accordingly.

100% agree with this. This was an oversight when I did the ASN model.

@DanSheps commented on GitHub (Jan 24, 2022): > LIRs own address space and ASN's. At least in North America, ASN's are only owned and managed by the RIR. LIR's do not handle ASNs. LIR's only handle allocations for sub-delegation. I don't think this relationship needs a model, as in most cases LIR's could be modelled by a "tenant" on a prefix. It looks like, at least for ASN's, APNIC, RIPE, LACNIC, and AFNIC are all the same Prefixes could be modelled differently, but it looks like at least a few use the RIR > NIC > LIR. I think it is easier to just model RIR. > With ASNs needing to be associated to a RIR, the RIR object view should be updated accordingly. 100% agree with this. This was an oversight when I did the ASN model.
adam commented 2025-12-29 19:35:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 30, 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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 30, 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:35:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 29, 2022):

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 (Jun 29, 2022): 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#5993
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?