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

Searching for IPv6 addresses in the global search should search for the compressed format #10843

New Issue
Closed
opened 2025-12-29 21:36:38 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:36:38 +01:00
Owner
Copy Link

Originally created by @kasimon on GitHub (Mar 5, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.2.4

Feature type

Change to existing functionality

Proposed functionality

Currently, when searching for ipv6 addresses in the global search, the user may only use the compressed ipv6 form (no leading zeros, multiple :0: blocks replaced by ::). My suggestion is that if the search term correctly parses as an ipv6 address, it should be internally normalized to the compressed form before sending it off to the search engine. Btw a similar correction already is in place with capital letters in ipv6 addresses, which are transparently converted to lower case letters.

Use case

When copying+pasting addresses or constructing search urls from other systems these systems may not always work with the compressed form, which causes the user to have to manually change the search term or being in the wrong impression that this ip address is not present in netbox, causing confusion or errors.

Database changes

None

External dependencies

None

Originally created by @kasimon on GitHub (Mar 5, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.2.4 ### Feature type Change to existing functionality ### Proposed functionality Currently, when searching for ipv6 addresses in the global search, the user may only use the compressed ipv6 form (no leading zeros, multiple `:0:` blocks replaced by `::`). My suggestion is that if the search term correctly parses as an ipv6 address, it should be internally normalized to the compressed form before sending it off to the search engine. Btw a similar correction already is in place with capital letters in ipv6 addresses, which are transparently converted to lower case letters. ### Use case When copying+pasting addresses or constructing search urls from other systems these systems may not always work with the compressed form, which causes the user to have to manually change the search term or being in the wrong impression that this ip address is not present in netbox, causing confusion or errors. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:36:38 +01:00
adam closed this issue 2025-12-29 21:36:38 +01:00
adam commented 2025-12-29 21:36:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 13, 2025):

We could introduce an attribute on the IPAddress model which returns the expanded form of an IPv6 address and include this as a cached value in the search indexer.

@jeremystretch commented on GitHub (Mar 13, 2025): We could introduce an attribute on the IPAddress model which returns the expanded form of an IPv6 address and include this as a cached value in the search indexer.
adam commented 2025-12-29 21:36:39 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 12, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 12, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
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 complexity: low status: accepted 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#10843
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?