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

Outer-VLAN-id added to vlan groups. #1482

New Issue
Closed
opened 2025-12-29 16:32:23 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:32:23 +01:00
Owner
Copy Link

Originally created by @funzoneq on GitHub (Jan 3, 2018).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.8

Description

I'd like to see support for 'vpls' vlan tagging in the vlan groups. Basically VPLS can have an inner vlan tag and an outer vlan tag. The combination of these two can be used to identify a unique customer. For example a group of switches gets Outer vlan ID 121 and on those switches customers get vlan 1-4096. The resulting packet will (for example) have Outer VLAN 121 and inner vlan 432.

The only thing we would need to add is a unique OutervlanID to the netbox/ipam/models.py. I have a patch ready to support this.

Originally created by @funzoneq on GitHub (Jan 3, 2018). ### Issue type [X] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> ### Environment * Python version: 3.5.2 * NetBox version: 2.2.8 <!-- BUG REPORTS must include: * A list of the steps needed for someone else to reproduce the bug * A description of the expected and observed behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description I'd like to see support for 'vpls' vlan tagging in the vlan groups. Basically VPLS can have an inner vlan tag and an outer vlan tag. The combination of these two can be used to identify a unique customer. For example a group of switches gets Outer vlan ID 121 and on those switches customers get vlan 1-4096. The resulting packet will (for example) have Outer VLAN 121 and inner vlan 432. The only thing we would need to add is a unique OutervlanID to the netbox/ipam/models.py. I have a patch ready to support this.
adam closed this issue 2025-12-29 16:32:23 +01:00
adam commented 2025-12-29 16:32:24 +01:00
Author
Owner
Copy Link

@funzoneq commented on GitHub (Jan 3, 2018):

https://github.com/digitalocean/netbox/compare/develop...paxio:183d93e0c802139435a37944fbc92124828dbe98

@funzoneq commented on GitHub (Jan 3, 2018): https://github.com/digitalocean/netbox/compare/develop...paxio:183d93e0c802139435a37944fbc92124828dbe98
adam commented 2025-12-29 16:32:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 10, 2018):

Custom fields are not supported on secondary models. Please see the FAQ.

@jeremystretch commented on GitHub (Jan 10, 2018): Custom fields are not supported on secondary models. Please see [the FAQ](https://github.com/digitalocean/netbox/wiki/Frequently-Asked-Questions#can-we-add-custom-fields-to-more-models).
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
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#1482
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?