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

Please display VLANs in Device -> Interface List #2002

New Issue
Closed
opened 2025-12-29 17:21:22 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:21:22 +01:00
Owner
Copy Link

Originally created by @tpo on GitHub (Sep 15, 2018).

Environment

  • Python version: 2.7.5
  • NetBox version: 2.3.1

A device includes a list view of its devices. it'd be very useful, if one could see in that view which VLAN(s) are on that interface.

Proposed Functionality

Allow the user to easily see the VLANs that are on an interface.

Use Case

I am configuring a device and assigning VLANs to its interfaces. Prior to deploying the changes into production, I want to make sure that the correct interfaces are assigned to each interface. Instead of iterating over each and every interface and clicking the edit button on each of the interfaces, just to see the VLANs attached to it I simply hover the mouse over the interface.

Database Changes

None

External Dependencies

None

Originally created by @tpo on GitHub (Sep 15, 2018). ### Environment * Python version: 2.7.5 * NetBox version: 2.3.1 A device includes a list view of its devices. it'd be very useful, if one could see in that view which VLAN(s) are on that interface. ### Proposed Functionality Allow the user to easily see the VLANs that are on an interface. ### Use Case I am configuring a device and assigning VLANs to its interfaces. Prior to deploying the changes into production, I want to make sure that the correct interfaces are assigned to each interface. Instead of iterating over each and every interface and clicking the edit button on each of the interfaces, just to see the VLANs attached to it I simply hover the mouse over the interface. ### Database Changes None ### External Dependencies None
adam closed this issue 2025-12-29 17:21:22 +01:00
adam commented 2025-12-29 17:21:22 +01:00
Author
Owner
Copy Link

@tpo commented on GitHub (Sep 15, 2018):

Instead of using my meager implementation, I suggest to use Paxio's version here: 293b2ea721 (see also the follow-up patches which fix and improve the functionality)

@tpo commented on GitHub (Sep 15, 2018): Instead of using my meager implementation, I suggest to use Paxio's version here: https://github.com/paxio/netbox/commit/293b2ea721f75acdafc5c78261328733ae1f5315 (see also the follow-up patches which fix and improve the functionality)
adam commented 2025-12-29 17:21:23 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Sep 15, 2018):

A new Interface view was implemented in v2.4.0 that includes the list of associated VLANs. Please upgrade to the latest version to use this view (currently 2.4.4).

In the future, only open issues and bug reports against the latest version of NetBox. This ensures the issue or bug being referenced has not already been resolved in the latest version.

@lampwins commented on GitHub (Sep 15, 2018): A new Interface view was implemented in v2.4.0 that includes the list of associated VLANs. Please upgrade to the latest version to use this view (currently 2.4.4). In the future, only open issues and bug reports against the latest version of NetBox. This ensures the issue or bug being referenced has not already been resolved in the latest version.
adam commented 2025-12-29 17:21:23 +01:00
Author
Owner
Copy Link

@tpo commented on GitHub (Nov 20, 2018):

A new Interface view was implemented in v2.4.0 that includes the list of associated VLANs. Please upgrade to the latest version to use this view (currently 2.4.4).

Thanks!

In the future, only open issues and bug reports against the latest version of NetBox. This ensures the issue or bug being referenced has not already been resolved in the latest version.

Will try

@tpo commented on GitHub (Nov 20, 2018): > A new Interface view was implemented in v2.4.0 that includes the list of associated VLANs. Please upgrade to the latest version to use this view (currently 2.4.4). Thanks! > In the future, only open issues and bug reports against the latest version of NetBox. This ensures the issue or bug being referenced has not already been resolved in the latest version. Will try
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#2002
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?