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 VLAN to device #9598

New Issue
Closed
opened 2025-12-29 21:19:31 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:19:31 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (May 7, 2024).

NetBox version

v4.0.0

Feature type

Change to existing functionality

Proposed functionality

Currently VLAN can be linked to interfaces (tagged and untagged).
My proposal is the ability to link VLANs to devices.

Use case

Not all vlans that are on an interface are actual vlans on the device. If you have a routed port with subinterfaces, then the vlan on the subinterface is never in the layer2 of the device.

Being able to link the vlans to a devices, tells me what VLANs I have to configure in the vlan database.

Another option would be a 'flag' or interfacetype that would tell that the vlan is not part of the layer2domain of the switch

The goals is the ability to generate VLAN configurations from the dcim, without over-creating vlans (like from the routed subinterface)

Database changes

No response

External dependencies

No response

Originally created by @PieterL75 on GitHub (May 7, 2024). ### NetBox version v4.0.0 ### Feature type Change to existing functionality ### Proposed functionality Currently VLAN can be linked to interfaces (tagged and untagged). My proposal is the ability to link VLANs to devices. ### Use case Not all vlans that are on an interface are actual vlans on the device. If you have a routed port with subinterfaces, then the vlan on the subinterface is never in the layer2 of the device. Being able to link the vlans to a devices, tells me what VLANs I have to configure in the vlan database. Another option would be a 'flag' or interfacetype that would tell that the vlan is not part of the layer2domain of the switch The goals is the ability to generate VLAN configurations from the dcim, without over-creating vlans (like from the routed subinterface) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 21:19:31 +01:00
adam closed this issue 2025-12-29 21:19:31 +01:00
adam commented 2025-12-29 21:19:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 21, 2024):

I believe this would be covered by #14451.

@jeremystretch commented on GitHub (May 21, 2024): I believe this would be covered by #14451.
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 status: duplicate 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#9598
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?