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

Assign ASN(s) to Provider Networks #7198

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

Originally created by @jvoss on GitHub (Nov 3, 2022).

NetBox version

v3.3.7

Feature type

Change to existing functionality

Proposed functionality

Add the ability to assign ASNs to Provider Networks directly.

Use case

Some providers have multiple ASNs. However the current implementation does not provide a mechanism to determine which ASN is used for each network.

The ability to associate one or more ASNs directly with a Provider Network removes this ambiguity.

For example, ISP A may provide Internet service using AS64512 but also provide L3VPN service using AS65000. Assigning both of these ASNs to the Provider object does not allow the ability to determine which ASN(s) are used on each network.

This is similar to #8496 but provides this functionality directly on the Provider Network level.

Database changes

  • Add ManyToMany relationship between ProviderNetwork and ipam.asn

External dependencies

None

Originally created by @jvoss on GitHub (Nov 3, 2022). ### NetBox version v3.3.7 ### Feature type Change to existing functionality ### Proposed functionality Add the ability to assign ASNs to Provider Networks directly. ### Use case Some providers have multiple ASNs. However the current implementation does not provide a mechanism to determine which ASN is used for each network. The ability to associate one or more ASNs directly with a `Provider Network` removes this ambiguity. For example, ISP A may provide Internet service using AS64512 but also provide L3VPN service using AS65000. Assigning both of these ASNs to the Provider object does not allow the ability to determine which ASN(s) are used on each network. This is similar to #8496 but provides this functionality directly on the Provider Network level. ### Database changes - Add `ManyToMany` relationship between `ProviderNetwork` and `ipam.asn` ### External dependencies None
adam added the type: featurepending closure labels 2025-12-29 20:20:22 +01:00
adam closed this issue 2025-12-29 20:20:22 +01:00
adam commented 2025-12-29 20:20:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 3, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 3, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:20:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 5, 2023):

Some providers have multiple ASNs.

In such case, it might be cleaner to create separate instances of the provider itself, denoting the different networks or services in use. They'll likely have e.g. different points of contact, etc. too

@jeremystretch commented on GitHub (Jan 5, 2023): > Some providers have multiple ASNs. In such case, it might be cleaner to create separate instances of the provider itself, denoting the different networks or services in use. They'll likely have e.g. different points of contact, etc. too
adam commented 2025-12-29 20:20:24 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 20, 2023):

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 (Mar 20, 2023): 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 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#7198
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?