Comment # 7
on bug 12022
from Michael Mann
The issue/shortcoming seems to be with find_conversation (or its use). Packet
7 is "smart" enough to create a new conversation, but packet 8 can't find it
(find_conversation returns the conversation used for packets 1-6).
The patch at https://code.wireshark.org/review/13381 starts to work towards a
solution by allowing the first conversation to be adjusted to have its last
packet be #6.
Maybe TCP flags need to be used more in determining which conversation the
packet should be using.
You are receiving this mail because:
- You are watching all bug changes.