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

IPAM | VRF add VNI field #11917

New Issue
Open
opened 2025-12-29 21:51:30 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:51:30 +01:00
Owner
Copy Link

Originally created by @c-po on GitHub (Dec 11, 2025).

NetBox version

v4.4.8

Feature type

Data model extension

Proposed functionality

VRFs already support assigning route-targets and route-distinguishers.

Use case

In EVPN VXLAN deployments a VRF also receives a VNI (VXLAN Network Identifier), add a VNI field with 24bit support

Database changes

No response

External dependencies

No response

Originally created by @c-po on GitHub (Dec 11, 2025). ### NetBox version v4.4.8 ### Feature type Data model extension ### Proposed functionality VRFs already support assigning route-targets and route-distinguishers. ### Use case In EVPN VXLAN deployments a VRF also receives a VNI (VXLAN Network Identifier), add a VNI field with 24bit support ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needednetbox labels 2025-12-29 21:51:30 +01:00
adam commented 2025-12-29 21:51:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 15, 2025):

VRFs already support assigning route-targets and route-distinguishers.

This does not introduce any new information. Please rewrite the "Proposed functionality" and "Database changes" sections above to specify the proposed implementation. What is the proposed field? How is it to be validated? Why should it go on the VRF model (as opposed to the L2VPN model)?

@jeremystretch commented on GitHub (Dec 15, 2025): > VRFs already support assigning route-targets and route-distinguishers. This does not introduce any new information. Please rewrite the "Proposed functionality" and "Database changes" sections above to specify the proposed implementation. What is the proposed field? How is it to be validated? Why should it go on the VRF model (as opposed to the L2VPN model)?
adam commented 2025-12-29 21:51:31 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 23, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Dec 23, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
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 netbox pending closure status: revisions needed 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#11917
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?