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

Filter subnets based on tenants #6811

New Issue
Closed
opened 2025-12-29 19:45:42 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:45:42 +01:00
Owner
Copy Link

Originally created by @Dirimsa on GitHub (Aug 15, 2022).

NetBox version

v3.2.8

Feature type

Change to existing functionality

Proposed functionality

Filter and assign subnets based on the tenant which it is assigned to.

When you have a huge network with multiple tenants which overlay some network areas then the child subnets are assigned to all the parent subnets and are not filtered any further.

  • Tenant A: 10.0.0.0/8
  • Tenant B: 10.0.0.0/8
  • Tenant C: 10.0.0.0/8
  • Tenant A First Subnet: - 10.120.24.0/22
  • Tenant A Second Subnet: -- 10.120.25.0/24

When you have a setup like the above the the 2 child subnets from Tenant A are assigned to the parent subnets of Tenant A and Tenant B and Tenant C as well.

Having a filter in place which assigns children based on the tenant would further increase the visibility and accessibility towards the data in a huge network environment.

Use case

Adding this functionality increases

  • visibility
  • data quality
  • tenant management with their subnets

in larger network areas which are assigned in netbox

Database changes

No response

External dependencies

No response

Originally created by @Dirimsa on GitHub (Aug 15, 2022). ### NetBox version v3.2.8 ### Feature type Change to existing functionality ### Proposed functionality Filter and assign subnets based on the tenant which it is assigned to. When you have a huge network with multiple tenants which overlay some network areas then the child subnets are assigned to all the parent subnets and are not filtered any further. - Tenant A: 10.0.0.0/8 - Tenant B: 10.0.0.0/8 - Tenant C: 10.0.0.0/8 - Tenant A First Subnet: - 10.120.24.0/22 - Tenant A Second Subnet: -- 10.120.25.0/24 When you have a setup like the above the the 2 child subnets from Tenant A are assigned to the parent subnets of Tenant A and Tenant B and Tenant C as well. Having a filter in place which assigns children based on the tenant would further increase the visibility and accessibility towards the data in a huge network environment. ### Use case Adding this functionality increases - visibility - data quality - tenant management with their subnets in larger network areas which are assigned in netbox ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:45:42 +01:00
adam closed this issue 2025-12-29 19:45:42 +01:00
adam commented 2025-12-29 19:45:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 16, 2022):

It's not clear from your description exactly what you're trying to accomplish. It looks like you have three tenants with overlapping IP space, in which case you'll need to use VRF assignment to create separate tables in addition to the tenant relationships.

@jeremystretch commented on GitHub (Aug 16, 2022): It's not clear from your description exactly what you're trying to accomplish. It looks like you have three tenants with overlapping IP space, in which case you'll need to use VRF assignment to create separate tables in addition to the tenant relationships.
adam commented 2025-12-29 19:45:43 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Aug 16, 2022):

I actually do exactly what Jeremy described. You create VRFs for each of your tenants because these actually represent different "realms", or routing space.
Tenancy has no meaning in routing. Route tables (VRFs) do.

@jsenecal commented on GitHub (Aug 16, 2022): I actually do exactly what Jeremy described. You create VRFs for each of your tenants because these actually represent different "realms", or routing space. Tenancy has no meaning in routing. Route tables (VRFs) do.
adam commented 2025-12-29 19:45:43 +01:00
Author
Owner
Copy Link

@Dirimsa commented on GitHub (Aug 16, 2022):

I can confirm that creating VRFs and assigning them to the prefixes gives me the desired result.

Thanks for the answer and solution provided.

@Dirimsa commented on GitHub (Aug 16, 2022): I can confirm that creating VRFs and assigning them to the prefixes gives me the desired result. Thanks for the answer and solution provided.
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 status: revisions needed 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#6811
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?