Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Assign VLAN to device #15985

Closed
PieterL75 opened this issue May 7, 2024 · 1 comment
Closed

Assign VLAN to device #15985

PieterL75 opened this issue May 7, 2024 · 1 comment
Labels
status: duplicate This issue has already been raised type: feature Introduction of new functionality to the application

Comments

@PieterL75
Copy link
Contributor

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
@PieterL75 PieterL75 added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels May 7, 2024
@arthanson arthanson added status: under review Further discussion is needed to determine this issue's scope and/or implementation and removed status: needs triage This issue is awaiting triage by a maintainer labels May 7, 2024
@arthanson arthanson removed their assignment May 7, 2024
@jeremystretch
Copy link
Member

I believe this would be covered by #14451.

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale May 21, 2024
@jeremystretch jeremystretch added status: duplicate This issue has already been raised and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: duplicate This issue has already been raised type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@arthanson @jeremystretch @PieterL75