Allow creation of virtual interfaces on virtual device context #144

New Issue

MrUnknownDE · 2026-04-05T16:22:13+02:00

MrUnknownDE commented

2026-04-05 16:22:13 +02:00

Originally created by @BrunoBlanes on 3/16/2026

NetBox version

v4.5.4

Feature type

Data model extension

Proposed functionality

Virtual device context should support independent virtual interface configurations, such as bridges, virtuals interfaces and link-aggregation groups.

Use case

Some systems, like Huawei's Versatile Routing Platform (VRP), supports mapping one or more physical or logical interfaces from the host device to the virtual context which in turn can do whatever it needs with those, including creating trunks around them with LACP and defining virtual sub-interfaces. These don't exist on the host device, only within the virtual context.

Right now, without this feature, it means that all interfaces must be declared on the host device, making for a messy documentation and almost impossible to replicate digital twin.

Database changes

I suppose you'll need only to update models for virtual device context and virtual interfaces.

External dependencies

Not applicable.

*Originally created by @BrunoBlanes on 3/16/2026* ### NetBox version v4.5.4 ### Feature type Data model extension ### Proposed functionality Virtual device context should support independent virtual interface configurations, such as bridges, virtuals interfaces and link-aggregation groups. ### Use case Some systems, like Huawei's Versatile Routing Platform (VRP), supports mapping one or more physical or logical interfaces from the host device to the virtual context which in turn can do whatever it needs with those, including creating trunks around them with LACP and defining virtual sub-interfaces. These don't exist on the host device, only within the virtual context. Right now, without this feature, it means that all interfaces must be declared on the host device, making for a messy documentation and almost impossible to replicate digital twin. ### Database changes I suppose you'll need only to update models for virtual device context and virtual interfaces. ### External dependencies Not applicable.

MrUnknownDE closed this issue

2026-04-05 16:22:13 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#144