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

Interface Bridges in Device Type #5898

New Issue
Closed
opened 2025-12-29 19:33:58 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:33:58 +01:00
Owner
Copy Link

Originally created by @PaulR282 on GitHub (Jan 7, 2022).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.1.4

Feature type

Change to existing functionality

Proposed functionality

Currently you can only bridge interfaces if the device already exists. It would be nice to "pre-bridge" interfaces in the device Type.

Use case

When you have devices like mediaconverter, currently you have to manually bridge the 2 interfaces after creating the device for every single device. It would be a lot easier to bridge the interfaces in the device type.

Database changes

No response

External dependencies

No response

Originally created by @PaulR282 on GitHub (Jan 7, 2022). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.1.4 ### Feature type Change to existing functionality ### Proposed functionality Currently you can only bridge interfaces if the device already exists. It would be nice to "pre-bridge" interfaces in the device Type. ### Use case When you have devices like mediaconverter, currently you have to manually bridge the 2 interfaces after creating the device for every single device. It would be a lot easier to bridge the interfaces in the device type. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:33:58 +01:00
adam closed this issue 2025-12-29 19:33:59 +01:00
adam commented 2025-12-29 19:33:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 9, 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 9, 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).
adam commented 2025-12-29 19:33:59 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Feb 15, 2023):

Just wanted to add that it would be nice to be able to do the same for Parent interface and LAG interface. I've run into both situations recently. On our aggregation switches, we create a LAG for the uplink and it would certainly save a step to have that already set up in the device template. The bigger issue I had recently was with the parent/child relationship, as we have some devices with bulk connectors that we currently model as a physical connector with virtual child interfaces under it and it's cumbersome having to remember to create those relationships each time a new device is added. Please let me know if I need to open a separate FR or if it's sufficient to update this one to include all the interface relationship types. I assume the implementation for one should be almost identical for the others, but maybe I'm missing something.

@sleepinggenius2 commented on GitHub (Feb 15, 2023): Just wanted to add that it would be nice to be able to do the same for *Parent interface* and *LAG interface*. I've run into both situations recently. On our aggregation switches, we create a LAG for the uplink and it would certainly save a step to have that already set up in the device template. The bigger issue I had recently was with the parent/child relationship, as we have some devices with bulk connectors that we currently model as a physical connector with virtual child interfaces under it and it's cumbersome having to remember to create those relationships each time a new device is added. Please let me know if I need to open a separate FR or if it's sufficient to update this one to include all the interface relationship types. I assume the implementation for one should be almost identical for the others, but maybe I'm missing something.
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 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#5898
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?