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

Folder-like prefix type? #6385

New Issue
Closed
opened 2025-12-29 19:40:06 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:40:06 +01:00
Owner
Copy Link

Originally created by @lamoni on GitHub (Apr 21, 2022).

NetBox version

v3.2.1

Feature type

New functionality

Proposed functionality

I think it would be useful if there were "folders" for prefixes for better top level organization or prefixes.

As an example, say our private space is 192.168.0.0/16, and then we have a lot of public /31s, and /30s that are given to us by a provider. When browsing to the prefix page, I would want to see just "Public" and "Private" folders, and within the Private folder is the 192.168.0.0/16 space and within the Public folder is the varying public IPs. Even if this was just for the top layer, it would be helpful.

As of right now, the varying public IPs we have muddies up the initial Prefixes page.

If anyone is familiar with Solarwinds IPAM, it would be the same thing as their "Group" or "Hierarchy Group" folders I think.

If there is interest in this, I wouldn't mind making an attempt at it.

Use case

Better organization for public vs private prefixes. Possibly improve loading time of the initial prefix page?

Database changes

Not sure

External dependencies

None that I know of

Originally created by @lamoni on GitHub (Apr 21, 2022). ### NetBox version v3.2.1 ### Feature type New functionality ### Proposed functionality I think it would be useful if there were "folders" for prefixes for better top level organization or prefixes. As an example, say our private space is 192.168.0.0/16, and then we have a lot of public /31s, and /30s that are given to us by a provider. When browsing to the prefix page, I would want to see just "Public" and "Private" folders, and within the Private folder is the 192.168.0.0/16 space and within the Public folder is the varying public IPs. Even if this was just for the top layer, it would be helpful. As of right now, the varying public IPs we have muddies up the initial Prefixes page. If anyone is familiar with Solarwinds IPAM, it would be the same thing as their "Group" or "Hierarchy Group" folders I think. If there is interest in this, I wouldn't mind making an attempt at it. ### Use case Better organization for public vs private prefixes. Possibly improve loading time of the initial prefix page? ### Database changes Not sure ### External dependencies None that I know of
adam added the type: feature label 2025-12-29 19:40:06 +01:00
adam closed this issue 2025-12-29 19:40:06 +01:00
adam commented 2025-12-29 19:40:06 +01:00
Author
Owner
Copy Link

@TheNetworkGuy commented on GitHub (Apr 21, 2022):

We migrated from phpIpam (which has this feature) to Netbox and we don't mis these roles at all. Actually i prefer the way Netbox handles the layout rendering with the IP CIDR model instead of manually grouping prefixes in a group. Since under the hood there were DB relationships with folders and ranges which were hard to move once locked in place.

You can search for private address spaces using RIR's, Agregates or even roles. That's how we use filtering on our network space.

@TheNetworkGuy commented on GitHub (Apr 21, 2022): We migrated from phpIpam (which has this feature) to Netbox and we don't mis these roles at all. Actually i prefer the way Netbox handles the layout rendering with the IP CIDR model instead of manually grouping prefixes in a group. Since under the hood there were DB relationships with folders and ranges which were hard to move once locked in place. You can search for private address spaces using RIR's, Agregates or even roles. That's how we use filtering on our network space.
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 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#6385
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?