 | 1 | initial version |
Any idea how to change the operation back to the old/useful way?
The only way to have the old behavior back is to have the code reverted or to add code to give an option to choose between the two ways to filter the conversation. Please do realize that using the tcp.stream way is more precise (in case of reused ports), but indeed local to one file.
A workaround would be to enable the calculation of the CommunityID. This can be done by going to Analyze -> Enabled Protocols and then enable it. The CommunityID is a hash of the 5-tuple designed to create an ID for each session that can be used across different Applications. So also between two Wireshark instances with different files.
Once the CommunityID protocol is enabled, each packet will contain this ID and it can be used to filter out a specific TCP or UDP session and the filter can be copied to other Wireshark instances and/or files :-)
