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

Setting VLAN Group/VLAN of Child Prefixes based on VLAN Group/VLAN assignment of parent prefix #2419

New Issue
Closed
opened 2025-12-29 17:25:57 +01:00 by adam · 2 comments
adam commented 2025-12-29 17:25:57 +01:00
Owner
Copy Link

Originally created by @joshniec on GitHub (Feb 28, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.1

Proposed Functionality

This proposal is to add functionality to automatically assign the VLAN Group/VLAN ID to child prefixes that are created under a prefix that is already assigned a VLAN Group and VLAN ID.

Use Case

I create an IP prefix of 192.168.0.0/24, and I assign this IP prefix to the following:

  • Tenant: ironick09
  • VLAN Group: ServerNetwork
  • VLAN ID: 5

Next, I create a child prefix that is under my previous prefix of 192.168.0.0/24. The child prefix I create is 192.168.0.0/26 (192.168.0.0-63). This might just be a pool, or something similar.

Current behavior when creating this child prefix is the fields VLAN Group and VLAN ID are by default left empty.

This feature request proposes auto populating these fields based on the VLAN Group and VLAN ID fields from the parent prefix.

Database Changes

None that I am aware of

External Dependencies

None that I am aware of.

Originally created by @joshniec on GitHub (Feb 28, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.5.1 ### Proposed Functionality This proposal is to add functionality to automatically assign the VLAN Group/VLAN ID to child prefixes that are created under a prefix that is already assigned a VLAN Group and VLAN ID. ### Use Case I create an IP prefix of 192.168.0.0/24, and I assign this IP prefix to the following: * Tenant: ironick09 * VLAN Group: ServerNetwork * VLAN ID: 5 Next, I create a child prefix that is under my previous prefix of 192.168.0.0/24. The child prefix I create is 192.168.0.0/26 (192.168.0.0-63). This might just be a pool, or something similar. Current behavior when creating this child prefix is the fields `VLAN Group` and `VLAN ID` are by default left empty. This feature request proposes auto populating these fields based on the `VLAN Group` and `VLAN ID` fields from the parent prefix. ### Database Changes None that I am aware of ### External Dependencies None that I am aware of.
adam closed this issue 2025-12-29 17:25:57 +01:00
adam commented 2025-12-29 17:25:57 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Feb 28, 2019):

Please see Jeremy's comments on #2887 (Prefilling Manufacturer for DeviceType).

As this would take considerable more effort, I don't think this is in the cards right now. Once the backlog is cleared, I this could be re-visited.

@DanSheps commented on GitHub (Feb 28, 2019): Please see Jeremy's comments on #2887 (Prefilling Manufacturer for DeviceType). As this would take considerable more effort, I don't think this is in the cards right now. Once the backlog is cleared, I this could be re-visited.
adam commented 2025-12-29 17:25:58 +01:00
Author
Owner
Copy Link

@joshniec commented on GitHub (Feb 28, 2019):

Thanks, I tried looking through the code to see if it was something I could tackle myself but I figured I’d post here first.

@joshniec commented on GitHub (Feb 28, 2019): Thanks, I tried looking through the code to see if it was something I could tackle myself but I figured I’d post here first.
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#2419
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?