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 support to designate dot1q vlan for L3 termination interface #11614

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

Originally created by @dmulyalin on GitHub (Sep 16, 2025).

NetBox version

v4.3.7

Feature type

Data model extension

Proposed functionality

Add support to designate vlan dot1q tag for L3 sub-interface

Use case

Sub-interfaces on devices are common and used for vlans (L2 domains) L3 termination, currently in Netbox there is no way to tell that interface terminates given vlan on L3 apart from encoding vlan id in interface name e.g. et-0/0/0.100

Using "802.1Q" mode "Vlan tagged" to associate with interface meant for L2 trunk interfaces and not for L3 interfaces. Suggest to add these "802.1Q Mode" modes:

  1. L3 Termination Access
  2. L3 Termination Tagged
  3. L3 Termination Q-in-Q

to account for most common scenarios of terminating layer 3 for the vlans.

Database changes

Not sure

External dependencies

Not sure

Originally created by @dmulyalin on GitHub (Sep 16, 2025). ### NetBox version v4.3.7 ### Feature type Data model extension ### Proposed functionality Add support to designate vlan dot1q tag for L3 sub-interface ### Use case Sub-interfaces on devices are common and used for vlans (L2 domains) L3 termination, currently in Netbox there is no way to tell that interface terminates given vlan on L3 apart from encoding vlan id in interface name e.g. et-0/0/0.100 Using "802.1Q" mode "Vlan tagged" to associate with interface meant for L2 trunk interfaces and not for L3 interfaces. Suggest to add these "802.1Q Mode" modes: 1. L3 Termination Access 2. L3 Termination Tagged 3. L3 Termination Q-in-Q to account for most common scenarios of terminating layer 3 for the vlans. ### Database changes Not sure ### External dependencies Not sure
adam added the netbox label 2025-12-29 21:47:40 +01:00
adam closed this issue 2025-12-29 21:47:41 +01:00
adam commented 2025-12-29 21:47:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 18, 2025):

currently in Netbox there is no way to tell that interface terminates given vlan on L3 apart from encoding vlan id in interface name e.g. et-0/0/0.100

Interface et-0/0/0.100 should be created as a virtual child interface of its parent (et0/0/0), with its 802.1Q mode set to "access" and its untagged VLAN selected accordingly.

@jeremystretch commented on GitHub (Sep 18, 2025): > currently in Netbox there is no way to tell that interface terminates given vlan on L3 apart from encoding vlan id in interface name e.g. et-0/0/0.100 Interface et-0/0/0.100 should be created as a virtual child interface of its parent (et0/0/0), with its 802.1Q mode set to "access" and its untagged VLAN selected accordingly.
adam commented 2025-12-29 21:47:41 +01:00
Author
Owner
Copy Link

@dmulyalin commented on GitHub (Sep 20, 2025):

Sorry, but have to argue that access and trunk terms are not applicable to L3 interfaces, workaround you describing can be used but on device doing either only L2 or only L3 subinterfaces, more accurate and less ambiguous way would be to designate L3 interface as terminating dot1q or qinq tags.

Having sub-interface in access or dot1q termination mode is needed when we try to render configurarion for interfaces on ios xr or juniper devices - within same device we could have all versions of vlan handling - access, trunk, L3 terminationon, sometimes even under same interface, without ability to designate switching as L3 dot1q termination we cannot distiguish interfaces mode and render configurarion appropriatly.

@dmulyalin commented on GitHub (Sep 20, 2025): Sorry, but have to argue that access and trunk terms are not applicable to L3 interfaces, workaround you describing can be used but on device doing either only L2 or only L3 subinterfaces, more accurate and less ambiguous way would be to designate L3 interface as terminating dot1q or qinq tags. Having sub-interface in access or dot1q termination mode is needed when we try to render configurarion for interfaces on ios xr or juniper devices - within same device we could have all versions of vlan handling - access, trunk, L3 terminationon, sometimes even under same interface, without ability to designate switching as L3 dot1q termination we cannot distiguish interfaces mode and render configurarion appropriatly.
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
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#11614
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?