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

Add ASNDOT notation column to ASN Ranges #11593

New Issue
Closed
opened 2025-12-29 21:47:20 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:47:20 +01:00
Owner
Copy Link

Originally created by @c-po on GitHub (Sep 10, 2025).

Originally assigned to: @pheus on GitHub.

NetBox version

v4.4.0

Feature type

Change to existing functionality

Proposed functionality

Netbox has great support for managing ASNs, ASN ranges and RIRs.

As we transition to 4-byte Autonomous System Numbers (ASNs), the representation and display of these values may become somewhat convoluted. This request focuses on modifying the user interface to improve how data is presented, rather than altering the underlying database storage.

Use case

Users should consistently view both the ASN number and its corresponding representation in ASDOT notation. While there is an option to display the ASDOT notation column within the ASNs section, this feature is currently unavailable for ASN ranges.

Image

When the ASDOT column is enabled in the ASN view, data duplication occurs, as 2-byte ASNs are displayed in the ASDOT column without any modification

Image

As network operators and engineers, I believe it would be advantageous for the "always enabled" ASN column to display the ASN followed by its ASDOT notation in parentheses, specifically for 4-byte ASNs. This approach mirrors the existing functionality when viewing individual ASNs in detail, enhancing clarity and consistency across the interface.

Image

Mockup

Image

Database changes

No response

External dependencies

No response

Originally created by @c-po on GitHub (Sep 10, 2025). Originally assigned to: @pheus on GitHub. ### NetBox version v4.4.0 ### Feature type Change to existing functionality ### Proposed functionality Netbox has great support for managing ASNs, ASN ranges and RIRs. As we transition to 4-byte Autonomous System Numbers (ASNs), the representation and display of these values may become somewhat convoluted. This request focuses on modifying the user interface to improve how data is presented, rather than altering the underlying database storage. ### Use case Users should consistently view both the ASN number and its corresponding representation in ASDOT notation. While there is an option to display the ASDOT notation column within the ASNs section, this feature is currently unavailable for ASN ranges. <img width="987" height="339" alt="Image" src="https://github.com/user-attachments/assets/01cb7756-0418-44e3-9b18-ab80c086699c" /> When the ASDOT column is enabled in the ASN view, data duplication occurs, as 2-byte ASNs are displayed in the ASDOT column without any modification <img width="993" height="533" alt="Image" src="https://github.com/user-attachments/assets/6317f741-44d2-4649-888c-cf013c5e31a0" /> As network operators and engineers, I believe it would be advantageous for the "always enabled" ASN column to display the ASN followed by its ASDOT notation in parentheses, specifically for 4-byte ASNs. This approach mirrors the existing functionality when viewing individual ASNs in detail, enhancing clarity and consistency across the interface. <img width="1065" height="524" alt="Image" src="https://github.com/user-attachments/assets/47adfbf4-da6b-47c1-a1aa-9a8ffcf49169" /> #### Mockup <img width="993" height="529" alt="Image" src="https://github.com/user-attachments/assets/f0d2e267-eedd-440d-a60a-0ad63efc8cc3" /> ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:47:20 +01:00
adam closed this issue 2025-12-29 21:47:20 +01:00
adam commented 2025-12-29 21:47:21 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 11, 2025):

For the table we wouldn't implement the " for the "always enabled" ASN column to display the ASN followed by its ASDOT notation in parentheses". That said in nod towards consistency we could add the ASDOT notation column to the ASN Ranges. Leaving this open for that specific change.

@arthanson commented on GitHub (Sep 11, 2025): For the table we wouldn't implement the " for the "always enabled" ASN column to display the ASN followed by its ASDOT notation in parentheses". That said in nod towards consistency we could add the ASDOT notation column to the ASN Ranges. Leaving this open for that specific change.
adam commented 2025-12-29 21:47:21 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Dec 17, 2025):

I'd like to contribute this enhancement. Could you please assign the issue to me? Thank you!

@pheus commented on GitHub (Dec 17, 2025): I'd like to contribute this enhancement. Could you please assign the issue to me? Thank you!
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 complexity: low netbox status: accepted 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#11593
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?