Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] TCP segmentation loss

From: "Anders Broman" <anders.broman@xxxxxxxxxxxx>
Date: Thu, 4 Jun 2009 10:29:20 +0200
Hi,
I think the TCP reassembly has problems with out-of-sequence messages.

Do you plan to submit your dissector to us? Which 3GPP protocol is it
for? You could submit the asn1 .cnf template files etc ( e.g the files
that go in /asn1/xx/) to be worked on in the SVN tree in that way we
could see the code and comment on it.
Regards
Anders

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Christopher
White (WTA)
Sent: den 4 juni 2009 09:29
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] TCP segmentation loss

Dear All,

I have recently been building a dissector for an 3GPP ASN.1 based
protocol which uses a tcp based transport.

I have followed the developer's guide (9.4) relating to the re-assembly
of fragments, and this seems to work fine.

However, after a tcp segment loss ( I have the preference analyse tcp
sequence no.  switched on), the ASN.1 BER PDUs are no longer detected
and decoded as expected. Somehow, synchronisation is lost. I presume
this is due to the sequence of segments on the wire.

I am new to building wireshark dissectors and with the ASN.1 tools. I
presume there is some additional logic required in my dissector - would
be very grateful if someone could point me in the right direction?

Best regards,
Chris

________________________________________________________________________
___
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe