 | 1 | initial version |
Is the trace taken natively (e.g., with tcpdump or Wireshark) or was it created by some other method?
I suspect it was created by another method and whatever is creating the trace is putting fake TCP headers that don't have correct sequence numbers.
Regardless you should probably be able to avoid the problem by disabling the TCP preference for analyzing sequence numbers.
ps. if you open a bug please be sure to post a link to it here.
