Issue when adding VLANs to an interface (tagged mode) #1424

New Issue

MrUnknownDE · 2026-04-06T01:12:26+02:00

MrUnknownDE commented

2026-04-06 01:12:26 +02:00

Originally created by @aseques on 8/20/2025

Deployment Type

Self-hosted

NetBox Version

v4.3.1

Python Version

3.10

Steps to Reproduce

I am trying to add the vlans to an interface, my desire would be to add them using the VID (instead of the internal ID number)

With the following query (extracted from the swagger sample) i ge

curl -X 'PATCH' \
  'https://netbox.example.com/api/dcim/interfaces/890/' \
  -H 'accept: application/json' \
  -H 'Authorization: 90b2c577da4bbd9bfbfb650c18e0a2a4d7e811d6' \
  -H 'Content-Type: application/json' \
  -H 'X-CSRFTOKEN: kv9maAk6k8CAhJbWrF8IXyy8JAYzIoYbARAPdEqQ80BzaozAc3q7hXCNhtGQ0Rrh' \
  -d '{
  "tagged_vlans": [
    32  ]
}'

I get this reply, becase the VLAN32 has the internal ID 22 (different from this one)

{
  "tagged_vlans": [
    "Invalid pk \"32\" - object does not exist."
  ]
}

Is there any way to PATCH the interface with the proper VLAN but using the VIDs?

Expected Behavior

VLAN 32 should be added to the interface

Observed Behavior

There's an error about the wrong ID for the VLAN given

*Originally created by @aseques on 8/20/2025* ### Deployment Type Self-hosted ### NetBox Version v4.3.1 ### Python Version 3.10 ### Steps to Reproduce I am trying to add the vlans to an interface, my desire would be to add them using the VID (instead of the internal ID number) With the following query (extracted from the swagger sample) i ge ``` curl -X 'PATCH' \ 'https://netbox.example.com/api/dcim/interfaces/890/' \ -H 'accept: application/json' \ -H 'Authorization: 90b2c577da4bbd9bfbfb650c18e0a2a4d7e811d6' \ -H 'Content-Type: application/json' \ -H 'X-CSRFTOKEN: kv9maAk6k8CAhJbWrF8IXyy8JAYzIoYbARAPdEqQ80BzaozAc3q7hXCNhtGQ0Rrh' \ -d '{ "tagged_vlans": [ 32 ] }' ``` I get this reply, becase the VLAN32 has the internal ID 22 (different from this one) ``` { "tagged_vlans": [ "Invalid pk \"32\" - object does not exist." ] } ``` Is there any way to PATCH the interface with the proper VLAN but using the VIDs? ### Expected Behavior VLAN 32 should be added to the interface ### Observed Behavior There's an error about the wrong ID for the VLAN given

MrUnknownDE closed this issue

2026-04-06 01:12:26 +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 pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug type: bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1424