Bridge members panel in interface view #5835

Closed
opened 2025-12-29 19:33:19 +01:00 by adam · 4 comments
Owner

Originally created by @candlerb on GitHub (Dec 23, 2021).

Originally assigned to: @stephanblanke on GitHub.

NetBox version

v3.1.2

Feature type

Change to existing functionality

Proposed functionality

When viewing interface details (e.g. /dcim/interfaces/3141/), there is a section for Child interfaces (i.e. other interfaces whose Parent points at this one), and a panel for LAG Members if the interface is a LAG. But bridge members are not shown.

I propose that if the interface type is "Bridge" then a Bridge Members panel is added - similar to the "LAG Members" panel - showing interfaces whose Bridge attribute points at this interface.

Use case

Be able to see and navigate to bridge member interfaces. Consistency with LAG member interfaces.

Workaround: you can manually enter URL /dcim/interfaces/?bridge_id=3141

Database changes

None

External dependencies

None

Originally created by @candlerb on GitHub (Dec 23, 2021). Originally assigned to: @stephanblanke on GitHub. ### NetBox version v3.1.2 ### Feature type Change to existing functionality ### Proposed functionality When viewing interface details (e.g. `/dcim/interfaces/3141/`), there is a section for Child interfaces (i.e. other interfaces whose Parent points at this one), and a panel for LAG Members if the interface is a LAG. But bridge members are not shown. I propose that if the interface type is "Bridge" then a Bridge Members panel is added - similar to the "LAG Members" panel - showing interfaces whose Bridge attribute points at this interface. ### Use case Be able to see and navigate to bridge member interfaces. Consistency with LAG member interfaces. Workaround: you can manually enter URL `/dcim/interfaces/?bridge_id=3141` ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:33:19 +01:00
adam closed this issue 2025-12-29 19:33:19 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 6, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 6, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@stephanblanke commented on GitHub (Mar 19, 2022):

I can try to implement this

@stephanblanke commented on GitHub (Mar 19, 2022): I can try to implement this
Author
Owner

@BrunoBlanes commented on GitHub (Apr 6, 2022):

Quick question, are the changes from 3.1.11 available in 3.2.0 given that both came out on the same day? If not, is there a timeline for it?

@BrunoBlanes commented on GitHub (Apr 6, 2022): Quick question, are the changes from 3.1.11 available in 3.2.0 given that both came out on the same day? If not, is there a timeline for it?
Author
Owner

@jeremystretch commented on GitHub (Apr 6, 2022):

@BrunoBlanes yes, all changes in v3.1.11 have been merged into v3.2.0.

@jeremystretch commented on GitHub (Apr 6, 2022): @BrunoBlanes yes, all changes in v3.1.11 have been merged into v3.2.0.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5835