Forced to set 802.1Q encapsulation when creating a new interface #1520

Closed
opened 2025-12-29 16:32:39 +01:00 by adam · 1 comment
Owner

Originally created by @jeremystretch on GitHub (Jan 30, 2018).

Issue type

[ ] Feature request
[x] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: v2.3-beta1

Description

The interface creation form requires the user to select an encapsulation mode of access, tagged, or tagged all. mode is an optional field and may be null (e.g. for routed interfaces).

Originally created by @jeremystretch on GitHub (Jan 30, 2018). ### Issue type [ ] Feature request <!-- An enhancement of existing functionality --> [x] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: v2.3-beta1 ### Description The interface creation form requires the user to select an encapsulation mode of access, tagged, or tagged all. `mode` is an optional field and may be null (e.g. for routed interfaces).
adam added the type: bugstatus: accepted labels 2025-12-29 16:32:39 +01:00
adam closed this issue 2025-12-29 16:32:39 +01:00
Author
Owner

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

Fixed in 2f7f5425d8

@jeremystretch commented on GitHub (Jan 30, 2018): Fixed in 2f7f5425d89abe2af2d11dabb2b774a62cf3aa05
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1520