Re: [Wireshark-dev] Problem due to segmentation of GTP packet.....

[prashanth joshi]

Hi,  one correction. It is not 5 CDR's in our GTP packet, but only cdr and within that there are 5 service records. 4 service records are displayed and the fifth service record is not displayed due to segmentation done by TCP.

Regards,

Prashanth.

prashanth joshi <[EMAIL PROTECTED]> wrote:

Hi all,

Please any one solve my problem. Every body here are struggling to solve it, but no body is getting the solution.

Regards,

Prashanth.

 

Our trace file contains 5 GCDR 's  within the same GTP packet.

The first four CDR's are correctly parsed. How ever the fifth is not at all displayed. It was observed that the tcp segmentation occured after the fourth cdr.

As a result the fifth CDR even though it is present in the data stream is not at all parsed by the ethereal.

It seems as TCP fragments are reassembled only at the destimation and ethereal sniffs packets off the wire even before the packets reach the destination ( ie within the n/w and not at the destination ) only the 4 cdr's are displayed. And the fifth cdr when it arrives in the stream much later is not recognized by the ethereal becos it can recognize the cdr only if there is gtp header attached to it.

The gtp header had arrived with the first four cdrs'. So ethereal does not recognize the fifth cdr as there is no gtp header with it.

So how to solve this problem...

Regards,

Prashanth

---

Everyone is raving about the all-new Yahoo! Mail._______________________________________________
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev

---

Want to start your own business? Learn how on Yahoo! Small Business.

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev