tcp.time_delta not filtering...

[Noel, Andre (6024395)]

Hello,

I was used to use a wonderful feature that permitted me to spot in a snap any latency greater than 500 ms in any tcp connection.
It seems to me it not working anymore and I got a message from wireshark about some obsolete thing in my color rules after trying to fix it...

Maybe I have to enable something else !? If you enter the filter, Wireshark takes it (green) but nothing happen.

My filter is: tcp.time_delta >= .500

Any though ?

Regards.
Andre N.

[Christopher Maynard]

Maybe I have to enable something else !?   If you enter the filter,

Wireshark takes it (green)  but nothing happen.

 
My filter is:   tcp.time_delta >= .500
 
Any though ?

You could try checking your TCP preferences, ensuring that "Calculate
conversation timestamps" is enabled.

If that doesn't solve your problem, then please supply, at the very least,
the specific version of Wireshark you're using. Even better would be to
provide all of the information displayed via `Help -> About Wireshark`.

- Chris


___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-***@wireshark.org>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-***@wireshark.org?s

[Noel, Andre (6024395)]

Maybe I have to enable something else !?   If you enter the filter,

Wireshark takes it (green)  but nothing happen.

 
My filter is:   tcp.time_delta >= .500
 
Any though ?

You could try checking your TCP preferences, ensuring that "Calculate conversation timestamps" is enabled.
If that doesn't solve your problem, then please supply, at the very least, the specific version of Wireshark you're using. Even better would be to provide all of the >information displayed via `Help -> About Wireshark`.
- Chris

Hello Chris,

I found my answer, thanks for your advice you sent my near the answer. I'm back on track.

Regards.


___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-***@wireshark.org>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wiresh

[Christopher Maynard]

Post by Noel, Andre (6024395)
I found my answer, thanks for your advice you sent my near the answer. I'm back on track.

Glad to hear it. For the benefit of others, especially Jeremy Fritts, maybe
you could post the solution that worked for you?

Thanks.
- Chris


___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users-IZ8446WsY0/***@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request-IZ8446WsY0/***@public.gmane.org?subject=unsubscribe

[Hugo van der Kooij]

This message contains a digitally signed email which can be read by opening the attachment.
Met vriendelijke groet,
With kind regards,




Qi ict

Delftechpark 35-37
Postbus 402, 2600 AK Delft


T : [phone]
F : [phone]
E : mailto:
I : http://www.qi.nl