Request ability to assign Vlans and default gateway to switches #1121

New Issue

adam · 2025-12-29T16:29:12+01:00

adam commented

2025-12-29 16:29:12 +01:00

Originally created by @jpatmore on GitHub (Jul 21, 2017).

Issue type:feature request

Python version:
NetBox version:

This may be related to feature request #1349 , but am raising it independently as I didnt want to dilute the excellent progress on that one (this is slightly different).

We too are developing Netbox as 'source of truth' for Ansible configuration management. We would like to assign existing site Vlans to a Layer 2 switch, and also assign the default gateway IP address.

For the Vlans. we are currently just manually creating virtual interfaces, and assigning them the ID of the Vlans (and then just leaving the IP field blank), It would be beneficial to be able to select in bulk from a check list of Vlans that exist at the site, and automatically create the interfaces with that Vlan ID, and add the Vlans name as description?

It would also be beneficial to assign the physical interfaces of the switch to either tagged/untagged status (untagged would mean a dot1q trunk), and assign physical interfaces as members of specific existing site Vlans in bulk.

For the default gateway, we would like to be able to select the interface of another device, and add it in the 'critical connections' section, as the 'default gateway' for the device.

These elements could then be called via API to populate the configuration variables in Ansible.

Thanks again for all the effort that is going in to this application.

Originally created by @jpatmore on GitHub (Jul 21, 2017).  ### Issue type:feature request  **Python version:** **NetBox version:**  This may be related to feature request #1349 , but am raising it independently as I didnt want to dilute the excellent progress on that one (this is slightly different). We too are developing Netbox as 'source of truth' for Ansible configuration management. We would like to assign existing site Vlans to a Layer 2 switch, and also assign the default gateway IP address. For the Vlans. we are currently just manually creating virtual interfaces, and assigning them the ID of the Vlans (and then just leaving the IP field blank), It would be beneficial to be able to select in bulk from a check list of Vlans that exist at the site, and automatically create the interfaces with that Vlan ID, and add the Vlans name as description? It would also be beneficial to assign the physical interfaces of the switch to either tagged/untagged status (untagged would mean a dot1q trunk), and assign physical interfaces as members of specific existing site Vlans in bulk. For the default gateway, we would like to be able to select the interface of another device, and add it in the 'critical connections' section, as the 'default gateway' for the device. These elements could then be called via API to populate the configuration variables in Ansible. Thanks again for all the effort that is going in to this application.

adam closed this issue

2025-12-29 16:29:12 +01:00

adam commented

2025-12-29 16:29:12 +01:00

@jeremystretch commented on GitHub (Jul 24, 2017):

We would like to assign existing site Vlans to a Layer 2 switch

#150 is open to assign VLANs to interfaces (e.g. tagged or untagged). It'll happen, we just haven't decided how yet. Once implemented, that information can be used to infer which VLANs should be configured on a switch.

and also assign the default gateway IP address

This is probably best handled by #1349. You could create a custom field for this in the interim, but IMO this is one of those miscellaneous bits in the config that you might want to share across multiple devices.

@jeremystretch commented on GitHub (Jul 24, 2017): > We would like to assign existing site Vlans to a Layer 2 switch #150 is open to assign VLANs to interfaces (e.g. tagged or untagged). It'll happen, we just haven't decided how yet. Once implemented, that information can be used to infer which VLANs should be configured on a switch. > and also assign the default gateway IP address This is probably best handled by #1349. You _could_ create a custom field for this in the interim, but IMO this is one of those miscellaneous bits in the config that you might want to share across multiple devices.

adam referenced this issue

2025-12-29 16:29:33 +01:00

Add Description or Comment to Inventory Items #1154

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#1121