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

Ability to sort and filter IP Address page #188

New Issue
Closed
opened 2025-12-29 16:19:06 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:19:06 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jul 10, 2016).

Would be helpful to be able to filter down based on certain filters or criteria, such as:

filter to 10.10.10.* only

Unused or used IPs only, possibly in combination with previous filter. (See #252)

This pertains mainly to the IP Address main screen (from the 'IP Space' menu), but would apply on other similar screens, such as from the IP Addresses tab of the Prefixes screen.

Originally created by @ghost on GitHub (Jul 10, 2016). Would be helpful to be able to filter down based on certain filters or criteria, such as: filter to 10.10.10.\* only Unused or used IPs only, possibly in combination with previous filter. (See #252) This pertains mainly to the IP Address main screen (from the 'IP Space' menu), but would apply on other similar screens, such as from the IP Addresses tab of the Prefixes screen.
adam added the type: feature label 2025-12-29 16:19:06 +01:00
adam closed this issue 2025-12-29 16:19:06 +01:00
adam commented 2025-12-29 16:19:07 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 13, 2016):

The best way to potentially do this would be to:

-populate the filter with the list of current aggregates under which the filtered prefix resides (/ipam/prefixes/)

-populate the filter with the list of current prefixes under which the filtered address resides (/ipam/ip-addresses/)

...mainly due to the aggregate -> prefix -> address workflow.

Would this be acceptable?

@bellwood commented on GitHub (Jul 13, 2016): The best way to potentially do this would be to: -populate the filter with the list of current aggregates under which the filtered prefix resides (/ipam/prefixes/) -populate the filter with the list of current prefixes under which the filtered address resides (/ipam/ip-addresses/) ...mainly due to the aggregate -> prefix -> address workflow. Would this be acceptable?
adam commented 2025-12-29 16:19:07 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 13, 2016):

Yeah, I think that would work. In our case, for example, we use two wildly different 10. IP schemes for primary and DR DCs. I think that's a good way to easily filter and drill down based on such a thing

@ghost commented on GitHub (Jul 13, 2016): Yeah, I think that would work. In our case, for example, we use two wildly different 10. IP schemes for primary and DR DCs. I think that's a good way to easily filter and drill down based on such a thing
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#188
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?