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

Adding 802.1x Radius VLAN as 802.1Q Mode #1637

New Issue
Closed
opened 2025-12-29 16:33:43 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:33:43 +01:00
Owner
Copy Link

Originally created by @cyberlu on GitHub (Mar 22, 2018).

Issue type

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

In our environment we have 802.1x with radius authentication.
It would be good if we had an option to add "802.1x" under "802.1Q Encapsulation" -> Mode
as in our scenario no unath VLAN is selectet the Port of the Switch is in no VLAN if the client cannot authenticat. The Client will be in one of the VLAN's depending on its Group. (no need to display this in Netbox)
In other cases (not our environment) when you select an UNAUTH-VID there should be an option to combine the Mode: 802.1x with a Untagged VLAN.

To display the VLAN-Tagging on the switch i already added to another post (This would be the best way to Display the VLAN participation in my opinion): https://github.com/digitalocean/netbox/issues/1945

The 802.1x would be displayed with an X instead of U for Untagged or T for Tagged.

Short Summary:
Please add under 802.1Q Encapsulation the Mode 802.1x and give the possibility to chose an Untagged VLAN for unauthorized Clients (use de Untagged VLAN Dropdown)

This should be easy to implement as it is just one entry more under 802.1Q Mode and with a little more work we could even get the unauthorized Untagged VLAN

With this implemented Netbox could hold the Data as we have it in our Running Config of our Switches.
We have Switches with clients and Access Points:
Port 1-20 is on 802.1x where Radius decides what VLAN will be used. Port 21 is fix Tagged to a few VLANs for the Access Point.

Environment

  • Python version: 3.5.2
  • NetBox version: 2.3.1
Originally created by @cyberlu on GitHub (Mar 22, 2018). ### Issue type [X] Feature request [ ] Bug report [ ] Documentation In our environment we have 802.1x with radius authentication. It would be good if we had an option to add "802.1x" under "802.1Q Encapsulation" -> Mode as in our scenario no unath VLAN is selectet the Port of the Switch is in no VLAN if the client cannot authenticat. The Client will be in one of the VLAN's depending on its Group. (no need to display this in Netbox) In other cases (not our environment) when you select an UNAUTH-VID there should be an option to combine the Mode: 802.1x with a Untagged VLAN. To display the VLAN-Tagging on the switch i already added to another post (This would be the best way to Display the VLAN participation in my opinion): https://github.com/digitalocean/netbox/issues/1945 The 802.1x would be displayed with an X instead of U for Untagged or T for Tagged. Short Summary: Please add under 802.1Q Encapsulation the Mode 802.1x and give the possibility to chose an Untagged VLAN for unauthorized Clients (use de Untagged VLAN Dropdown) This should be easy to implement as it is just one entry more under 802.1Q Mode and with a little more work we could even get the unauthorized Untagged VLAN With this implemented Netbox could hold the Data as we have it in our Running Config of our Switches. We have Switches with clients and Access Points: Port 1-20 is on 802.1x where Radius decides what VLAN will be used. Port 21 is fix Tagged to a few VLANs for the Access Point. ### Environment * Python version: 3.5.2 * NetBox version: 2.3.1
adam closed this issue 2025-12-29 16:33:43 +01:00
adam commented 2025-12-29 16:33:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 29, 2018):

There isn't anything special about a VLAN used for 802.1X; it's just another tagged VLAN on the interface. You can use a different mechanism, such as a custom field or object tag (#132) to identify 802.1X VLANs for configuration rendering.

@jeremystretch commented on GitHub (Mar 29, 2018): There isn't anything special about a VLAN used for 802.1X; it's just another tagged VLAN on the interface. You can use a different mechanism, such as a custom field or object tag (#132) to identify 802.1X VLANs for configuration rendering.
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#1637
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?