Separate IP addresses in the menu into two types: ipv4 and ipv6. #10342

Closed
opened 2025-12-29 21:30:17 +01:00 by adam · 3 comments
Owner

Originally created by @click0 on GitHub (Oct 10, 2024).

NetBox version

4.1.3

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

Separate IP addresses in the menu into two types: ipv4 and ipv6.

Use case

In the networks of large operators, this will significantly speed up the visual search of IP addresses.

Database changes

No response

External dependencies

No response

Originally created by @click0 on GitHub (Oct 10, 2024). ### NetBox version 4.1.3 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality Separate IP addresses in the menu into two types: ipv4 and ipv6. ### Use case In the networks of large operators, this will significantly speed up the visual search of IP addresses. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetbox labels 2025-12-29 21:30:17 +01:00
adam closed this issue 2025-12-29 21:30:17 +01:00
Author
Owner

@jsenecal commented on GitHub (Oct 10, 2024):

Just use a saved search filter?
image

@jsenecal commented on GitHub (Oct 10, 2024): Just use a saved search filter? ![image](https://github.com/user-attachments/assets/741c2141-8e5a-4645-84b2-f827f3dbc332)
Author
Owner

@click0 commented on GitHub (Oct 10, 2024):

As an option and compromise, add saved filters using Netbox (not the browser!)
изображение

@click0 commented on GitHub (Oct 10, 2024): As an option and compromise, add saved filters using Netbox (not the browser!) ![изображение](https://github.com/user-attachments/assets/100cfea5-2143-4bfa-9227-92ff619cbe0d)
Author
Owner

@bctiemann commented on GitHub (Feb 6, 2025):

This doesn't seem like a good reason for the necessary duplication of functionality; it isn't a pattern we want to follow to create distinct concrete models for objects that are otherwise identical but can be differentiated by a filter. We'd recommend using a saved filter as suggested above.

@bctiemann commented on GitHub (Feb 6, 2025): This doesn't seem like a good reason for the necessary duplication of functionality; it isn't a pattern we want to follow to create distinct concrete models for objects that are otherwise identical but can be differentiated by a filter. We'd recommend using a saved filter as suggested above.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10342