Comment # 6
on bug 12855
from Pascal Quantin
For both cases, 2.0.5 behavior seems better (as discussed in Gerrit I'm not a
fan of the reassembly happening despite missing packets).
Maybe that's why previous code was not simple ;)
IMHO the Follow TCP stream feature should not rely on the upper dissector
having TCP reassembly activated / supported or not.
Not sure how to move forward. Obviously the current handling needs more work,
and the previous code was working fine for those use cases. Should we revert
the change until a more solid version is available? Michael, what's your
opinion?
You are receiving this mail because:
- You are watching all bug changes.
