starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow multiple physical interfaces to be assigned to a bridge #9449

New Issue
Closed
opened 2025-12-29 20:50:04 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:50:04 +01:00
Owner
Copy Link

Originally created by @skutter-de on GitHub (Apr 6, 2024).

NetBox version

v3.7.5

Feature type

Data model extension

Proposed functionality

I want to be able to assign multiple physical interfaces to a bridge interface

Use case

I have a MikroTik Router. You allow switching between groups by creating a bridge. This bridge get the physical ports assigned to it. I want to be able to replicate this in NetBox so I can implement this with my automation.

Database changes

The "Bridged Interface" field would need to be turned into a list.

External dependencies

No response

Originally created by @skutter-de on GitHub (Apr 6, 2024). ### NetBox version v3.7.5 ### Feature type Data model extension ### Proposed functionality I want to be able to assign multiple physical interfaces to a bridge interface ### Use case I have a MikroTik Router. You allow switching between groups by creating a bridge. This bridge get the physical ports assigned to it. I want to be able to replicate this in NetBox so I can implement this with my automation. ### Database changes The "Bridged Interface" field would need to be turned into a list. ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:50:04 +01:00
adam closed this issue 2025-12-29 20:50:04 +01:00
adam commented 2025-12-29 20:50:05 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 9, 2024):

Thanks for your interest in improving NetBox.

The functionality you propose already exists. This is just a case of the workflow for populating a bridge working in a way that differs from your expectation.

To model a multiaccess bridged segment, first create a virtual interface (e.g. br0) of type Bridge. Then, in a separate step, set the Bridged interface attribute of each member physical interface (e.g. eth0, eth1...) to the virtual bridge interface previously created. Now if you visit the details of br0 you'll see eth0 and eth1 listed under the Bridge Interfaces heading.

@jeffgdotorg commented on GitHub (Apr 9, 2024): Thanks for your interest in improving NetBox. The functionality you propose already exists. This is just a case of the workflow for populating a bridge working in a way that differs from your expectation. To model a multiaccess bridged segment, first create a virtual interface (e.g. `br0`) of type Bridge. Then, in a separate step, set the *Bridged interface* attribute of each member physical interface (e.g. `eth0`, `eth1`...) to the virtual bridge interface previously created. Now if you visit the details of `br0` you'll see `eth0` and `eth1` listed under the *Bridge Interfaces* heading.
adam commented 2025-12-29 20:50:05 +01:00
Author
Owner
Copy Link

@skutter-de commented on GitHub (Apr 9, 2024):

This should really be documented.

A "How do I document xxx" section in the docs would be really cool

@skutter-de commented on GitHub (Apr 9, 2024): This should really be documented. A "How do I document xxx" section in the docs would be really cool
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 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#9449
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?