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

Interface Import - Add VLAN import #8801

New Issue
Closed
opened 2025-12-29 20:41:19 +01:00 by adam · 14 comments
adam commented 2025-12-29 20:41:19 +01:00
Owner
Copy Link

Originally created by @N0odlez on GitHub (Nov 2, 2023).

Originally assigned to: @pheus on GitHub.

NetBox version

v3.6.4

Feature type

New functionality

Proposed functionality

I would like to see the Interface import function support the changing of the vlans tagged and the default vlan. This will help bulk update saving time. It will also help with new people joining the Netbox community to be able to import their infrastructure quicker and easier.

Use case

Currently there is no way to bulk import interfaces and assign the vlan at the same time

Database changes

No response

External dependencies

No response

Originally created by @N0odlez on GitHub (Nov 2, 2023). Originally assigned to: @pheus on GitHub. ### NetBox version v3.6.4 ### Feature type New functionality ### Proposed functionality I would like to see the Interface import function support the changing of the vlans tagged and the default vlan. This will help bulk update saving time. It will also help with new people joining the Netbox community to be able to import their infrastructure quicker and easier. ### Use case Currently there is no way to bulk import interfaces and assign the vlan at the same time ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 20:41:19 +01:00
adam closed this issue 2025-12-29 20:41:20 +01:00
adam commented 2025-12-29 20:41:20 +01:00
Author
Owner
Copy Link

@jdavidson2021 commented on GitHub (Jan 2, 2024):

I agree that the assignment of VLANs to interfaces is the biggest usability issue that we have with NetBox. We can import pretty much everything with CSV, except for the assignment of VLANs to an interface. This is currently a very manual process using the UI to bulk edit the interfaces on a device in order to assign the VLANs to interfaces on a network device. It is very tedious and error prone.

@jdavidson2021 commented on GitHub (Jan 2, 2024): I agree that the assignment of VLANs to interfaces is the biggest usability issue that we have with NetBox. We can import pretty much everything with CSV, except for the assignment of VLANs to an interface. This is currently a very manual process using the UI to bulk edit the interfaces on a device in order to assign the VLANs to interfaces on a network device. It is very tedious and error prone.
adam commented 2025-12-29 20:41:21 +01:00
Author
Owner
Copy Link

@mrclschstr commented on GitHub (Feb 1, 2024):

Currently we use the Netbox API as a workaround, but a bulk import with the specification of VLAN IDs would simplify the process a lot.

@mrclschstr commented on GitHub (Feb 1, 2024): Currently we use the Netbox API as a workaround, but a bulk import with the specification of VLAN IDs would simplify the process a lot.
adam commented 2025-12-29 20:41:21 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 15, 2024):

any possibility of this making it into 4.0.x or the 4.1 train?
Running into this now with a new implementation of netbox with about 800 VM's. We can import the interfaces with the mode, but not the untagged vlan, or the multiple tagged vlans.

@ghost commented on GitHub (Jul 15, 2024): any possibility of this making it into 4.0.x or the 4.1 train? Running into this now with a new implementation of netbox with about 800 VM's. We can import the interfaces with the mode, but not the untagged vlan, or the multiple tagged vlans.
adam commented 2025-12-29 20:41:21 +01:00
Author
Owner
Copy Link

@proy-rbbn commented on GitHub (Sep 6, 2024):

I am hoping since you can bulk-edit vlans it isn't too much work to allow bulk-import of the same thing.... could someone pick that up in 4.1?

@proy-rbbn commented on GitHub (Sep 6, 2024): I am hoping since you can bulk-edit vlans it isn't too much work to allow bulk-import of the same thing.... could someone pick that up in 4.1?
adam commented 2025-12-29 20:41:22 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Apr 25, 2025):

Hi @jeremystretch , I’d be interested in contributing this feature. I noticed it’s not marked “needs owner” - would it be okay for me to take it on?

Also, should support for Q-in-Q be included as part of this?

Lastly, I assume this feature request applies to VMInterface as well - is that correct?

@pheus commented on GitHub (Apr 25, 2025): Hi @jeremystretch , I’d be interested in contributing this feature. I noticed it’s not marked “needs owner” - would it be okay for me to take it on? Also, should support for Q-in-Q be included as part of this? Lastly, I assume this feature request applies to `VMInterface` as well - is that correct?
adam commented 2025-12-29 20:41:25 +01:00
Author
Owner
Copy Link

@sepetuks commented on GitHub (Aug 21, 2025):

Just stumbled on this limitation as well and wonder if this is in near plans to be implemented?

@sepetuks commented on GitHub (Aug 21, 2025): Just stumbled on this limitation as well and wonder if this is in near plans to be implemented?
adam commented 2025-12-29 20:41:26 +01:00
Author
Owner
Copy Link

@BartZimmo commented on GitHub (Oct 14, 2025):

@jeremystretch Any news if @pheus can help with this feature?
The ability to update the tagged VLANs on interfaces would be a big addition to bulk import/update.

@BartZimmo commented on GitHub (Oct 14, 2025): @jeremystretch Any news if @pheus can help with this feature? The ability to update the tagged VLANs on interfaces would be a big addition to bulk import/update.
adam commented 2025-12-29 20:41:26 +01:00
Author
Owner
Copy Link

@ifoughal commented on GitHub (Oct 30, 2025):

I've stumbled on this as of today as well and would be happy to contribute if need be.

@ifoughal commented on GitHub (Oct 30, 2025): I've stumbled on this as of today as well and would be happy to contribute if need be.
adam commented 2025-12-29 20:41:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 30, 2025):

@BartZimmo @ifoughal would either of you like to volunteer to own this issue and submit a PR?

@jeremystretch commented on GitHub (Oct 30, 2025): @BartZimmo @ifoughal would either of you like to volunteer to own this issue and submit a PR?
adam commented 2025-12-29 20:41:26 +01:00
Author
Owner
Copy Link

@ifoughal commented on GitHub (Oct 31, 2025):

Hi @jeremystretch , would be happy to contribute! I can start working on it next week.

@ifoughal commented on GitHub (Oct 31, 2025): Hi @jeremystretch , would be happy to contribute! I can start working on it next week.
adam commented 2025-12-29 20:41:27 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Oct 31, 2025):

Hi @ifoughal and maintainers,

Back in April 2025, when I first offered to contribute on this issue, I put together a working patch to add tagged/untagged VLAN fields to the Interface and VMInterface CSV imports (tests included). If no one else has started and @ifoughal is okay with it, I’m happy to open a PR to finish this off. If you’d prefer to take it, I’m glad to collaborate or share my branch so we can co‑author - whatever works best. Thanks!

@pheus commented on GitHub (Oct 31, 2025): Hi @ifoughal and maintainers, Back in April 2025, when I first offered to contribute on this issue, I put together a working patch to add tagged/untagged VLAN fields to the Interface and VMInterface CSV imports (tests included). If no one else has started and @ifoughal is okay with it, I’m happy to open a PR to finish this off. If you’d prefer to take it, I’m glad to collaborate or share my branch so we can co‑author - whatever works best. Thanks!
adam commented 2025-12-29 20:41:27 +01:00
Author
Owner
Copy Link

@ifoughal commented on GitHub (Oct 31, 2025):

Hi @ifoughal and maintainers,

Back in April 2025, when I first offered to contribute on this issue, I put together a working patch to add tagged/untagged VLAN fields to the Interface and VMInterface CSV imports (tests included). If no one else has started and @ifoughal is okay with it, I’m happy to open a PR to finish this off. If you’d prefer to take it, I’m glad to collaborate or share my branch so we can co‑author - whatever works best. Thanks!

I'm ok with it, please do open the PR & thank you for your contribution!

@ifoughal commented on GitHub (Oct 31, 2025): > Hi [@ifoughal](https://github.com/ifoughal) and maintainers, > > Back in April 2025, when I first offered to contribute on this issue, I put together a working patch to add tagged/untagged VLAN fields to the Interface and VMInterface CSV imports (tests included). If no one else has started and [@ifoughal](https://github.com/ifoughal) is okay with it, I’m happy to open a PR to finish this off. If you’d prefer to take it, I’m glad to collaborate or share my branch so we can co‑author - whatever works best. Thanks! I'm ok with it, please do open the PR & thank you for your contribution!
adam commented 2025-12-29 20:41:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 31, 2025):

Thanks @pheus, I've assigned this to you.

@jeremystretch commented on GitHub (Oct 31, 2025): Thanks @pheus, I've assigned this to you.
adam commented 2025-12-29 20:41:27 +01:00
Author
Owner
Copy Link

@jdavidson2021 commented on GitHub (Dec 23, 2025):

I'm very glad to see this feature implemented. Thanks to everyone that played a part. This is a significant upgrade when it comes to usability and the assignment of VLANs to interfaces.

@jdavidson2021 commented on GitHub (Dec 23, 2025): I'm very glad to see this feature implemented. Thanks to everyone that played a part. This is a significant upgrade when it comes to usability and the assignment of VLANs to interfaces.
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 complexity: low netbox 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#8801
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?