Just to add to this a bit.
the valid operators for addr is in/notin, however an eq statement can also be used in the GUI. The GUI is presently set so that if you run a query with the eq operator ( addr.dst eq 10.191.16.61 ) it truly uses the CLI equivelent of 'show log traffic dst in 10.191.16.61' and essentially "corrects" your operator issue for you. The same was never setup for a neq operator, simply hitting the invalid operator warning.
Essentially this was done to be friendly to operator mistakes, but it can also easily lead to confusion since the operator overwrite was never fully fleshed out to include all operators.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!