Search result show both 2 added prefixes 10.200.0.0/24 and 10.200.2.0/24
Search result show only one prefix 10.200.0.0/24
This is not a bug. When searching by prefix, the provided ID is cast as a prefix. In this example, "10.200" is interpreted as "10.200.0.0", which is why 10.200.2.0 is not matched.
I could have swore this worked before, did this get changed recently? Would we maybe want to not cast it as a prefix?
Just checked this on an old v2.5.0, worked the same way then.
Add new :
Then search "10.200", results are :
There you miss the prefix 10.200.2.0/24, and you get the IP address 10.200.2.1/24 which match the missed prefix.
Prefixes search behavior is not the same as IP addresses search, looks like a bug to me, at least confusing for user.
How to search all prefixes and IP addresses matching 10.200.*.* ?
Did this have to be a search functionality evolution ?
could you just search 10.200.0.0/22 or something larger?
could you just search
10.200.0.0/22or something larger?
"10.200.0.0/22" search response is :
"10.200.0.0/8" search response is : "no result found"
You want the "search within" field located directly below the general search field on the prefixes list. For example, ?within_include=10.200.0.0/22 will return all prefixes within 10.200.0.0/22 (as well as 10.200.0.0/22 itself, if it exists).
One search, two behaviors, depending if it applies to prefixes/aggregates or ip addresses.
Looks like a bug to me, but if you decide it is a "functionality" so it is.