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

Adding Tenant's ASN selection to an IP address and Circuit #6370

New Issue
Closed
opened 2025-12-29 19:39:56 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:39:56 +01:00
Owner
Copy Link

Originally created by @MarianRychtecky on GitHub (Apr 18, 2022).

NetBox version

v3.1.9

Feature type

Change to existing functionality

Proposed functionality

In our case, it would be very useful to have a selection (drop-down) menu for Tenant's ASN within IP address screen. This will allow us to assign certain Tenant ASN to IP address. The Tenant group and Tenant are already on the screen.The same thing would be nice on the Circuit definition screen.

163609069-f53d52b9-e7a6-4680-aefd-118f3f99bd3d

163609244-b6500446-49ea-4e91-91d3-19f6c9cc587d

Use case

All our members/customers are having a BGP peering with us and our route servers, having ASN associated with an IP address and circuit I can have a configuration parameter for other components. Some members/customers have multiple ASNs therefore we need to extend this association within IP address and Circuit.

Database changes

Add Tenant's ASN relation to IP address
Add Tenant's ASN relation to Circuit

External dependencies

Nothing I'm aware of.

Originally created by @MarianRychtecky on GitHub (Apr 18, 2022). ### NetBox version v3.1.9 ### Feature type Change to existing functionality ### Proposed functionality In our case, it would be very useful to have a selection (drop-down) menu for Tenant's ASN within IP address screen. This will allow us to assign certain Tenant ASN to IP address. The Tenant group and Tenant are already on the screen.The same thing would be nice on the Circuit definition screen. ![163609069-f53d52b9-e7a6-4680-aefd-118f3f99bd3d](https://user-images.githubusercontent.com/36925394/163826155-95ab2b5b-1188-4974-be03-d23436aa61a5.png) ![163609244-b6500446-49ea-4e91-91d3-19f6c9cc587d](https://user-images.githubusercontent.com/36925394/163826219-5437b57d-b715-4315-a9ec-d522a1695af5.png) ### Use case All our members/customers are having a BGP peering with us and our route servers, having ASN associated with an IP address and circuit I can have a configuration parameter for other components. Some members/customers have multiple ASNs therefore we need to extend this association within IP address and Circuit. ### Database changes Add Tenant's ASN relation to IP address Add Tenant's ASN relation to Circuit ### External dependencies Nothing I'm aware of.
adam added the type: featurepending closure labels 2025-12-29 19:39:56 +01:00
adam closed this issue 2025-12-29 19:39:56 +01:00
adam commented 2025-12-29 19:39:57 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 18, 2022):

I don't see us adding ASN to these views at all, if I am being honest.

While they may bring value, for service providers in certain circumstances, the majority of our user base are not service providers. For non service provider users, ASN on IP address (and to a lesser extent Circuits) make no sense.

Additionally, both the Circuit and the IP Address are the wrong place to attempt to model your routing policy. Until we do something with routing policy in core, or someone builds a plugin, you are welcome to use a custom field for this which references the ASN model.

@DanSheps commented on GitHub (Apr 18, 2022): I don't see us adding ASN to these views at all, if I am being honest. While they may bring value, for service providers in certain circumstances, the majority of our user base are not service providers. For non service provider users, ASN on IP address (and to a lesser extent Circuits) make no sense. Additionally, both the Circuit and the IP Address are the wrong place to attempt to model your routing policy. Until we do something with routing policy in core, or someone builds a plugin, you are welcome to use a custom field for this which references the ASN model.
adam commented 2025-12-29 19:39:57 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 18, 2022):

Thank you for submitting your idea. Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.

@DanSheps commented on GitHub (Apr 18, 2022): Thank you for submitting your idea. Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.
adam commented 2025-12-29 19:39:57 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Apr 25, 2022):

This can be accomplished using the Custom Object Fields introduced in v3.2

https://docs.netbox.dev/en/stable/customization/custom-fields/#custom-object-fields

image

@tyler-8 commented on GitHub (Apr 25, 2022): This can be accomplished using the Custom Object Fields introduced in v3.2 https://docs.netbox.dev/en/stable/customization/custom-fields/#custom-object-fields ![image](https://user-images.githubusercontent.com/17618971/165164300-c7348d36-76e6-43b7-adbe-287eaa166013.png)
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 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#6370
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?