Re: Dissecting a Protocol with multiple static TCP ports

[Craig Bumpstead <cbumpste () yahoo com au>]

Bill,

The packets that are not decoded are decoded as TCP packets. So I don't understand why it only decodes the first one. I 
must be making a mistake in the code.

Regards,
Craig




----- Original Message ----
From: Bill Meier <wmeier () newsguy com>
To: Developer support list for Wireshark <wireshark-dev () wireshark org>
Sent: Tue, 27 April, 2010 11:10:14 AM
Subject: Re: [Wireshark-dev] Dissecting a Protocol with multiple static TCP ports

Craig Bumpstead wrote:
> Bill,
>
> Thanks for the quick response. That setting is off.
> The first and second packets are TCP port 4435 and 21016 which it decodes.
> However from that point on it doesn't decode packets with
> TCP port 4435.
>
> I loath posting my code, but obviously I am making a mistake somewhere.

I don't see anything obviously wrong with the code.

A question: What is actually shown in Wireshark for the packets not 
decoded ?

Are they decoded as TCP ? As some other protocol ?



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



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