https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16037
--- Comment #5 from Oliver-Tobias Ripka <o...@bockcay.de> ---
So my confusion was due to different settings for "Allow subdissector to
reassemble TCP streams"
Frame #811 gets dissected as HTTP in Wireshark when TCP reassembly is turned on
and behaves the same as sharkd when reassembly is turned off (811 is dissected
as TCP and 810 is dissected as HTTP instead).
So I went on to tested different settings of TCP reassembly in sharkd and could
not get it to have the same behavior as Wireshark
For example with these commands:
{"req": "load", "file": "./sharkd-issue.pcap"}
{"req": "setconf", "name": "tcp.desegment_tcp_streams", "value": "TRUE"}
{"req": "dumpconf", "pref": "tcp.desegment_tcp_streams"}
{"req": "frame", "frame": "811", "proto": 1}
{"req": "load", "file": "./sharkd-issue.pcap"}
{"req": "setconf", "name": "tcp.desegment_tcp_streams", "value": "FALSE"}
{"req": "dumpconf", "pref": "tcp.desegment_tcp_streams"}
{"req": "frame", "frame": "811", "proto": 1}
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
