Wildcard search within Network Rules
If I go to IP Host and filter by "Port", I see everything containing that keyword. However, if I go to edit a Network Rule in Policies and type in "Port" in the Networks search box, I get no results. In the Networks search box I seem to be unable to find anything unless I know the beginning name of the network I wish to search for. In this case, I have to enter "#Port." IMHO it would be better if the search term was treated as an "include" type match versus a "begins with" search.
A nightmare to search hosts, networks etc. . Please implement wildcards or a good search like search in SG..
Chris Gundry commented
Please implement this, it is a nightmare at the moment!
When working in a firewall rule the options settings search should search the whole field and not just if it starts the string. Example: Destination networks- search for Filewave, internal_Filewave will not show up. Anything with the search string in it should show up.
Currently partial matches do not yield results if the filter doesn't start the same way as the criterion.
"and" will show "Andorra"
"dorra" will not show anything (i.e. "Andorra" is not shown)
"la" will show "LAN"
"an" will not show "LAN"
When creating a new firewall rule, when a user clicks on the "Add New Item" button for zones or source networks and devices, the search box should filter and match based on "contains" instead of only the starting portion of the object name. When using a standard naming convention for objects, often many objects have the same prefix. I shouldn't have to type out the whole prefix just to find the object I'm looking for.
Mike Bell commented
This needs to be added. Any of the drop-down searches should be include, not starts-with. Its useless as is. We have so many services/ip hosts/etc and currently are forced to scroll if you dont know the name.
Svein olav Lybekk commented
Please Add this.
Editing/creating rules will be a nightmare when you start to get alot of definitions.