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

ASN Range check does not satisfy IANA ASN distribution #9256

New Issue
Closed
opened 2025-12-29 20:47:32 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:47:32 +01:00
Owner
Copy Link

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

Deployment Type

Self-hosted

NetBox Version

v3.7.2

Python Version

3.9

Steps to Reproduce

  1. Add new ASN range;
  2. Insert RIPE-2 ASN range start (2043) and end (2043) values (according to https://www.iana.org/assignments/as-numbers/as-numbers.xml);
  3. Submit form.

Expected Behavior

Since IANA assigned several single-AS ranges (e. g. 2043, 2047) to RIPE i propose:

  • either allow range start value to be less or equal to range end value (preferred);
  • or make range end value to be not mandatory.

Observed Behavior

ASN Range form throws "Starting ASN (2043) must be lower than ending ASN (2043)." error message.

Originally created by @kornix on GitHub (Feb 16, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.2 ### Python Version 3.9 ### Steps to Reproduce 1. Add new ASN range; 2. Insert RIPE-2 ASN range start (2043) and end (2043) values (according to https://www.iana.org/assignments/as-numbers/as-numbers.xml); 3. Submit form. ### Expected Behavior Since IANA assigned several single-AS ranges (e. g. 2043, 2047) to RIPE i propose: - either allow range start value to be less **or equal** to range end value (preferred); - or make range end value to be not mandatory. ### Observed Behavior ASN Range form throws "Starting ASN (2043) must be lower than ending ASN (2043)." error message.
adam closed this issue 2025-12-29 20:47:32 +01:00
adam commented 2025-12-29 20:47:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 16, 2024):

This is not a bug: An range of ASNs (or really any type of object) requires a separate starting and ending value. Instead, you should create this as a single ASN if you need to track it.

@jeremystretch commented on GitHub (Feb 16, 2024): This is not a bug: An range of ASNs (or really any type of object) requires a separate starting and ending value. Instead, you should create this as a single ASN if you need to track it.
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#9256
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?