Re: [Wireshark-dev] TCP reassembly and Return value of a new-style dissector

2014-12-10 Thread Peter Wu
On Wednesday 10 December 2014 16:56:30 Anders Broman wrote: > >> I think the ultimate solution would be for the TCP dissector to call > >> the SIP dissector again with the next incomplete PDU after receiving > >> the number of bytes "accepted" by the SIP dissector e.g using the > >> "new-style d

Re: [Wireshark-dev] TCP reassembly and Return value of a new-style dissector

2014-12-10 Thread Anders Broman
-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Peter Wu Sent: den 10 december 2014 17:17 To: wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] TCP reassembly and Return value of a new-style dissector On

Re: [Wireshark-dev] TCP reassembly and Return value of a new-style dissector

2014-12-10 Thread Peter Wu
On Tuesday 09 December 2014 21:01:37 Anders Broman wrote: > Hi, > I have recently come across some problems with reassembly of SIP > messages over TCP. One problem seems to be related to when a segment > contains one full PDU and a segment of the next (following) PDU (in > this case the first SIP

[Wireshark-dev] TCP reassembly and Return value of a new-style dissector

2014-12-09 Thread Anders Broman
Hi, I have recently come across some problems with reassembly of SIP messages over TCP one problem seems to be related to when a segment contains one full PDU and a segment of the next following PDU in this case the first SIP line of the following PDU is not complete. I think the ultimate sol