IP allocation skips ASN #9257

Closed
opened 2025-12-29 20:47:32 +01:00 by adam · 5 comments
Owner

Originally created by @craigmcfly on GitHub (Feb 16, 2024).

NetBox version

v3.7.1

Feature type

New functionality

Proposed functionality

A prefix is assigned by the RIR to an LIR (usually a one to one mapping between LIR and ASN), but the IPAM doesn't allow prefixes to be assigned to be ASNs, nor can you se a list of assigned prefixes from the ASN page ( https://netbox.mydomain.com/ipam/asns/1/ )

It would be nice if prefixes ( https://netbox.mydomain.com/ipam/aggregates/?rir_id=1 ) could be allocated.

Use case

It would help when working down from the ASN level to see assigned prefixes

Database changes

No response

External dependencies

No response

Originally created by @craigmcfly on GitHub (Feb 16, 2024). ### NetBox version v3.7.1 ### Feature type New functionality ### Proposed functionality A prefix is assigned by the RIR to an LIR (usually a one to one mapping between LIR and ASN), but the IPAM doesn't allow prefixes to be assigned to be ASNs, nor can you se a list of assigned prefixes from the ASN page ( https://netbox.mydomain.com/ipam/asns/1/ ) It would be nice if prefixes ( https://netbox.mydomain.com/ipam/aggregates/?rir_id=1 ) could be allocated. ### Use case It would help when working down from the ASN level to see assigned prefixes ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:47:32 +01:00
adam closed this issue 2025-12-29 20:47:33 +01:00
Author
Owner

@PieterL75 commented on GitHub (Mar 20, 2024):

I had the same issue submitted some time ago:
https://github.com/netbox-community/netbox/issues/8782
But linking prefixes to ASN's was not implemented because "there is no direct relationship between a prefix and an ASN in reality". I hope you can convince them that within a LIR the relation is real and very important (RPKI/ROA)
Then there is https://github.com/netbox-community/netbox/issues/9828 that gets more in details on LIR/ROA, but that was set to be a plugin rather than native to the netbox core...

I would still really like to get the ASN linked to a Prefix, as that is pretty basic. The ROA/RPKI part then get into a pluging

@PieterL75 commented on GitHub (Mar 20, 2024): I had the same issue submitted some time ago: https://github.com/netbox-community/netbox/issues/8782 But linking prefixes to ASN's was not implemented because "there is no direct relationship between a prefix and an ASN in reality". I hope you can convince them that within a LIR the relation is real and very important (RPKI/ROA) Then there is https://github.com/netbox-community/netbox/issues/9828 that gets more in details on LIR/ROA, but that was set to be a plugin rather than native to the netbox core... I would still really like to get the ASN linked to a Prefix, as that is pretty basic. The ROA/RPKI part then get into a pluging
Author
Owner

@falz commented on GitHub (Mar 26, 2024):

This has come up repeatedly, there are many use cases to assign IP to ASN. In addition to that RPKI issue there are many other tools, such as bgpalerter, who's config file correlates IPs to ASNs.

We were just looking to use Netbox export templates to build a Bgpalerter config, but it does not seem possible due to this lack of relationship.

@falz commented on GitHub (Mar 26, 2024): This has come up repeatedly, there are many use cases to assign IP to ASN. In addition to that RPKI issue there are many other tools, such as bgpalerter, who's config file correlates IPs to ASNs. We were just looking to use Netbox export templates to build a Bgpalerter config, but it does not seem possible due to this lack of relationship.
Author
Owner

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

It seems that several proposed functionalities are being conflated in the conversation above. The issue title reads "IP allocation skips ASN" (?) yet the description references both prefixes and aggregates. @craigmcfly could you please edit your post above (do not make a new reply) to clarify the specific proposal?

@jeremystretch commented on GitHub (Apr 4, 2024): It seems that several proposed functionalities are being conflated in the conversation above. The issue title reads "IP allocation skips ASN" (?) yet the description references both prefixes and aggregates. @craigmcfly could you please edit your post above (do not make a new reply) to clarify the _specific_ proposal?
Author
Owner

@arthanson commented on GitHub (May 15, 2024):

@craigmcfly can you please edit the post above to clarify the specific proposal? Issue is pending closure without additional updates.

@arthanson commented on GitHub (May 15, 2024): @craigmcfly can you please edit the post above to clarify the specific proposal? Issue is pending closure without additional updates.
Author
Owner

@arthanson commented on GitHub (May 17, 2024):

Closing as no feedback.

@arthanson commented on GitHub (May 17, 2024): Closing as no feedback.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9257