starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Edit on multiple Interface does not allow to set VLANs #6078

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

Originally created by @basti1508 on GitHub (Feb 11, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.7

Python version

3.9

Steps to Reproduce

  • Open Interface view of device
  • select 2-n interfaces
  • click on edit
  • select e.g. Untagged VLAN
  • click save

Expected Behavior

the vlan will be added to the interface

Observed Behavior

nothing happens.
It is also not possible to select the 802.1q switching type in that view (which may cause this error)

Originally created by @basti1508 on GitHub (Feb 11, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.7 ### Python version 3.9 ### Steps to Reproduce - Open Interface view of device - select 2-n interfaces - click on edit - select e.g. Untagged VLAN - click save ### Expected Behavior the vlan will be added to the interface ### Observed Behavior nothing happens. It is also not possible to select the 802.1q switching type in that view (which may cause this error)
adam added the type: bugstatus: accepted labels 2025-12-29 19:36:30 +01:00
adam closed this issue 2025-12-29 19:36:31 +01:00
adam commented 2025-12-29 19:36:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 15, 2022):

VLANs can be assigned only to interfaces with their mode set to one of the 802.1Q options (untagged, tagged, or tagged-all). When an interface with its mode set to None is saved, any VLANs associated with it are automatically removed. I can confirm that specifying the mode when assigning the untagged VLAN functions as expected.

Granted, the bulk edit form should at least throw a validation error to avoid confusion. I can take that.

@jeremystretch commented on GitHub (Feb 15, 2022): VLANs can be assigned only to interfaces with their mode set to one of the 802.1Q options (untagged, tagged, or tagged-all). When an interface with its mode set to `None` is saved, any VLANs associated with it are [automatically removed](https://github.com/netbox-community/netbox/blob/18eb9ffae61368c1e895e2d383c096592c4ebe3f/netbox/dcim/models/device_components.py#L492-L494). I can confirm that specifying the mode when assigning the untagged VLAN functions as expected. Granted, the bulk edit form should at least throw a validation error to avoid confusion. I can take that.
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: accepted type: bug
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#6078
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?