We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi.
When I set a filter pressing 'f' like the following:
ip.src == 10.0.0.1
pcap-mode displays the corresponding packets perfectly.
But if I do:
ip.src == 10.0.0.1 && ip.dst == 10.0.0.2
Then, it seems that it is not honoring the second filter. It displays packets going to other ip's.
I have tried with parens, like the following: (ip.src == 10.0.0.1) && (ip.dst == 10.0.0.2)
But it complains saying that parens are not allowed (although they are valid on tshark).
Thanks. -Bob
The text was updated successfully, but these errors were encountered:
Okay - I know the issue. I don't have a good solution yet, but give me a few days. meanwhile, enclose your filter in quotes.
ex: "ip.src == 10.0.0.1 && ip.dst == 10.0.0.2" instead of ip.src == 10.0.0.1 && ip.dst == 10.0.0.2
That should be the workaround for now. I'll fix it soon.
Sorry, something went wrong.
Yeah, I have used double quotes and it works ok.
Thanks.
No branches or pull requests
Hi.
When I set a filter pressing 'f' like the following:
ip.src == 10.0.0.1
pcap-mode displays the corresponding packets perfectly.
But if I do:
ip.src == 10.0.0.1 && ip.dst == 10.0.0.2
Then, it seems that it is not honoring the second filter. It displays packets going to other ip's.
I have tried with parens, like the following:
(ip.src == 10.0.0.1) && (ip.dst == 10.0.0.2)
But it complains saying that parens are not allowed (although they are valid on tshark).
Thanks.
-Bob
The text was updated successfully, but these errors were encountered: