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

Add support for bridge interfaces #1343

New Issue
Closed
opened 2025-12-29 16:31:36 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:31:36 +01:00
Owner
Copy Link

Originally created by @patrick7 on GitHub (Oct 20, 2017).

Issue type

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

Description

On a router I have some bridges with multiple interfaces.
With Netbox it's possible to assign an IP address to the (virtual) bridge interface, but it is not possible to reflect which interface is in which bridge. There should be a possibility similar to the bonding devices.

Originally created by @patrick7 on GitHub (Oct 20, 2017). ### Issue type [x] Feature request [ ] Bug report [ ] Documentation ### Description On a router I have some bridges with multiple interfaces. With Netbox it's possible to assign an IP address to the (virtual) bridge interface, but it is not possible to reflect which interface is in which bridge. There should be a possibility similar to the bonding devices.
adam closed this issue 2025-12-29 16:31:36 +01:00
adam commented 2025-12-29 16:31:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 26, 2017):

NetBox doesn't support modeling bridges. This is one of those things that crosses into general configuration management and we have to avoid falling down that rabbit hole.

@jeremystretch commented on GitHub (Oct 26, 2017): NetBox doesn't support modeling bridges. This is one of those things that crosses into general configuration management and we have to avoid falling down that rabbit hole.
adam commented 2025-12-29 16:31:37 +01:00
Author
Owner
Copy Link

@patrick7 commented on GitHub (Oct 26, 2017):

So how do you recommend to document the IPs on bridges? (virtual interfaces?) And how to reflect interfaces in a bridge?

There is a possibility for LAG interfaces, something similar for bridges would be perfect (like master / child interfaces).

@patrick7 commented on GitHub (Oct 26, 2017): So how do you recommend to document the IPs on bridges? (virtual interfaces?) And how to reflect interfaces in a bridge? There is a possibility for LAG interfaces, something similar for bridges would be perfect (like master / child interfaces).
adam commented 2025-12-29 16:31:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 26, 2017):

You can create a virtual interface named e.g. BVI1 to represent a bridge group and assign IP addresses to it. NetBox does not model bridge groups, but maybe #150 will help once it's been implemented.

@jeremystretch commented on GitHub (Oct 26, 2017): You can create a virtual interface named e.g. `BVI1` to represent a bridge group and assign IP addresses to it. NetBox does not model bridge groups, but maybe #150 will help once it's been implemented.
adam commented 2025-12-29 16:31:37 +01:00
Author
Owner
Copy Link

@patrick7 commented on GitHub (Oct 26, 2017):

How can I assign the physical interfaces to BVI1?

That's possible for LAGs - why not for bridges?
I need to reflect which interface is in which bridge, similar to LAGs & LAG members.

@patrick7 commented on GitHub (Oct 26, 2017): How can I assign the physical interfaces to BVI1? That's possible for LAGs - why not for bridges? I need to reflect which interface is in which bridge, similar to LAGs & LAG members.
adam commented 2025-12-29 16:31:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 26, 2017):

Conceptually, a bridge group is the same as a VLAN. Let's see how #150 plays out and you can ask to reopen this issue if it still does not meet your needs.

@jeremystretch commented on GitHub (Oct 26, 2017): Conceptually, a bridge group is the same as a VLAN. Let's see how #150 plays out and you can ask to reopen this issue if it still does not meet your needs.
adam commented 2025-12-29 16:31:38 +01:00
Author
Owner
Copy Link

@alexjhart commented on GitHub (Dec 23, 2019):

#150 is implemented and works great. I'd love to see bridge modeling added. It would work almost identically to LAG modeling, so I expect most of the code would be recycled from that. There are network devices, like Mikrotik routers and switches, that heavily incorporate bridges into the VLAN and port configuration (ports are added to a bridge, VLANs are added to bridge and bridge ports, not the physical interfaces), so I don't see this as any less relevant to include than LAG and VLAN in Netbox. Right now, I'm trying to model a bridge, which contains LAGs and other ports which also manages VLANs for the bridge ports and CPU. I can almost fudge this with LAGs, but LAGs can't have parent LAGs. If I use a virtual interface, I can't track which bridge ports are part of. I would also like to show bridge configuration on hypervisors. Can we please re-open this @jeremystretch ?

@alexjhart commented on GitHub (Dec 23, 2019): #150 is implemented and works great. I'd love to see bridge modeling added. It would work almost identically to LAG modeling, so I expect most of the code would be recycled from that. There are network devices, like Mikrotik routers and switches, that heavily incorporate bridges into the VLAN and port configuration (ports are added to a bridge, VLANs are added to bridge and bridge ports, not the physical interfaces), so I don't see this as any less relevant to include than LAG and VLAN in Netbox. Right now, I'm trying to model a bridge, which contains LAGs and other ports which also manages VLANs for the bridge ports and CPU. I can almost fudge this with LAGs, but LAGs can't have parent LAGs. If I use a virtual interface, I can't track which bridge ports are part of. I would also like to show bridge configuration on hypervisors. Can we please re-open this @jeremystretch ?
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#1343
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?