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

Feature Req: Possibility to define bridges and other virt. ifaces and attach these to LAGs, ... #1624

New Issue
Closed
opened 2025-12-29 16:33:35 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:33:35 +01:00
Owner
Copy Link

Originally created by @scotty00X on GitHub (Mar 16, 2018).

Issue type

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

Hi,
I like to submit the following feature request:

  • more specific virtual interfaces types aka 'Form Factor' for bridges, vlan other than the provided 'other'-type
  • the possibility to attach these to a parent interface. Right now it is possible only to attach to 'Parent LAG'
  • to connect LAGs to each other for documentation / visualization

Perhaps a picture says more ...
netbox-define-bridge-on-lag

Kind regards,
Henrik

Originally created by @scotty00X on GitHub (Mar 16, 2018). **Issue type** [x] Feature request [ ] Bug report [ ] Documentation Hi, I like to submit the following feature request: - more specific virtual interfaces types aka 'Form Factor' for bridges, vlan other than the provided 'other'-type - the possibility to attach these to a parent interface. Right now it is possible only to attach to 'Parent LAG' - to connect LAGs to each other for documentation / visualization Perhaps a picture says more ... ![netbox-define-bridge-on-lag](https://user-images.githubusercontent.com/37411806/37518580-08d64b5c-2916-11e8-838d-dd8ec745ded3.png) Kind regards, Henrik
adam closed this issue 2025-12-29 16:33:35 +01:00
adam commented 2025-12-29 16:33:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 19, 2018):

From the contributing guide:

Good feature requests are very narrowly defined. Be sure to thoroughly describe the functionality and data model(s) being proposed. The more effort you put into writing a feature request, the better its chance is of being implemented. Overly broad feature requests will be closed.

Please modify your issue to address only one specific feature request.

@jeremystretch commented on GitHub (Mar 19, 2018): From [the contributing guide](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md): > Good feature requests are very narrowly defined. Be sure to thoroughly describe the functionality and data model(s) being proposed. The more effort you put into writing a feature request, the better its chance is of being implemented. Overly broad feature requests will be closed. Please modify your issue to address only one specific feature request.
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#1624
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?