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

Show reverse bridge relationships on interface detail pages #11911

New Issue
Open
opened 2025-12-29 21:51:27 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:51:27 +01:00
Owner
Copy Link

Originally created by @arthanson on GitHub (Dec 9, 2025).

Originally assigned to: @kprince28 on GitHub.

NetBox version

v4.4.8

Feature type

Change to existing functionality

Proposed functionality

When an interface’s Bridged interface is set to another interface, only the source interface shows this relationship. The target interface has no indication that anything is bridged to it.

  1. Create two interfaces "int-A" and "int-B"
  2. on "int-A" set Bridged Interface to "int-B"
  3. Look on the detail view of Int-A and under Related Interfaces it shows Bridge pointing to Int-B
  4. Go to the detail page of Int-B and under Related Interfaces there is no indication that it has a Bridge

Use case

Operators visiting the physical NIC cannot see which virtual interfaces depend on it without API queries or manually checking other interfaces.

Database changes

None

External dependencies

None

Originally created by @arthanson on GitHub (Dec 9, 2025). Originally assigned to: @kprince28 on GitHub. ### NetBox version v4.4.8 ### Feature type Change to existing functionality ### Proposed functionality When an interface’s Bridged interface is set to another interface, only the source interface shows this relationship. The target interface has no indication that anything is bridged to it. 1. Create two interfaces "int-A" and "int-B" 2. on "int-A" set Bridged Interface to "int-B" 3. Look on the detail view of Int-A and under Related Interfaces it shows Bridge pointing to Int-B 4. Go to the detail page of Int-B and under Related Interfaces there is no indication that it has a Bridge ### Use case Operators visiting the physical NIC cannot see which virtual interfaces depend on it without API queries or manually checking other interfaces. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:51:27 +01:00
adam commented 2025-12-29 21:51:28 +01:00
Author
Owner
Copy Link

@kprince28 commented on GitHub (Dec 18, 2025):

@arthanson Can you assign this to me?

@kprince28 commented on GitHub (Dec 18, 2025): @arthanson Can you assign this to me?
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 complexity: low netbox status: accepted type: feature
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#11911
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?