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 prefixes by aggregate #2126

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

Originally created by @Jamie- on GitHub (Nov 15, 2018).

Environment

  • Python version: 3.6.6
  • NetBox version: 2.4.7

Proposed Functionality

Add ability to be able to filter prefixes by aggregate using the search pane on the right-hand side.

Use Case

When using multiple RFC 1918 private IP spaces it would be nice to be able to filter down the list of prefixes by the scope of private space. For example show only the 10.0.0.0/8 prefixes or only the 192.168.0.0/16 prefixes.

Database Changes

I don't believe so, all the data required exists already. All this feature adds is a new filter.

External Dependencies

None

Originally created by @Jamie- on GitHub (Nov 15, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.6 * NetBox version: 2.4.7 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Add ability to be able to filter prefixes by aggregate using the search pane on the right-hand side. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case When using multiple RFC 1918 private IP spaces it would be nice to be able to filter down the list of prefixes by the scope of private space. For example show only the 10.0.0.0/8 prefixes or only the 192.168.0.0/16 prefixes. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes I don't believe so, all the data required exists already. All this feature adds is a new filter. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 17:22:30 +01:00
adam commented 2025-12-29 17:22:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 15, 2018):

The within and within_include filters are available for this purpose. For example:

/ipam/prefixes/?within_include=10.0.0.0/8
@jeremystretch commented on GitHub (Nov 15, 2018): The `within` and `within_include` filters are available for this purpose. For example: ``` /ipam/prefixes/?within_include=10.0.0.0/8 ```
adam commented 2025-12-29 17:22:30 +01:00
Author
Owner
Copy Link

@Jamie- commented on GitHub (Nov 16, 2018):

Is there a way to do this only from the filter pane on the right hand side?

@Jamie- commented on GitHub (Nov 16, 2018): Is there a way to do this only from the filter pane on the right hand side?
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#2126
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?