Skip to content

Tagged VLANs not showing in interface table when using 802.1Q Mode = Q-in-Q (802.1ad). #18376

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
Closed
Chiniquy opened this issue Jan 10, 2025 · 0 comments · Fixed by #18377
Closed

Tagged VLANs not showing in interface table when using 802.1Q Mode = Q-in-Q (802.1ad). #18376

Chiniquy opened this issue Jan 10, 2025 · 0 comments · Fixed by #18377
Assignees
@jeremystretch
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Chiniquy
Copy link

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v.4.2.0

Python Version

3.10

Steps to Reproduce

  1. Create VLAN 1 (name Test1)
  2. Create VLAN 200 (name Test2) with QinQ role Service
  3. Create a device (name Test Device)
  4. Create a Ethernet (fixed) interface with 802.1Q Mode = QinQ
  5. On this interface, set Tagged VLAN = Test1 and Service VLAN = Test2
  6. Go to the Interface table of the device, and note that while the Service VLAN for this interface is visible, the Tagged VLAN is not.

I thought that I might need to assign VLAN Test1 to QinQ Role = Customer and QinQ SVLAN = Test2, but doing this did not change anything, the bug still occurs.

Expected Behavior

I expect the Tagged VLANs selected on the interface to be visible in the Tagged VLANs column.

Observed Behavior

No VLANs are visible in the Tagged VLANs column.
@Chiniquy Chiniquy added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 10, 2025
@jeremystretch jeremystretch self-assigned this Jan 10, 2025
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Jan 10, 2025
jeremystretch added a commit that referenced this issue Jan 10, 2025
@jeremystretch
Fixes #18376: Include tagged VLANs in interfaces list for Q-in-Q inte…
8bb1a68 
…rfaces
@jeremystretch jeremystretch mentioned this issue Jan 10, 2025
Merged
@jeremystretch jeremystretch mentioned this issue Jan 17, 2025
Merged
bctiemann pushed a commit that referenced this issue Jan 28, 2025
@jeremystretch @bctiemann
Fixes #18376: Include tagged VLANs in interfaces list for Q-in-Q inte…
6ba9c3c 
…rfaces
bctiemann pushed a commit that referenced this issue Jan 29, 2025
@jeremystretch @bctiemann
Fixes #18376: Include tagged VLANs in interfaces list for Q-in-Q inte…
56ae573 
…rfaces
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes #18376: Include tagged VLANs in interfaces list for Q-in-Q interfaces netbox-community/netbox
2 participants
@Chiniquy @jeremystretch