Re: need to read three bytes of offset

[prashanth joshi <prashanthsjoshi2000 () yahoo com>]

Hi Guy Harris,
 
thanks for the clarification. 
I was writing a function to read such 3 byte values and convert them to int. Unaware that uint24 field is supported in 
C (I have seen uint24 field only in wireshark). 
Now I am using the uint24 type.
 
Regards,
Prashanth

--- On Thu, 3/4/10, Guy Harris <guy () alum mit edu> wrote:


From: Guy Harris <guy () alum mit edu>
Subject: Re: [Wireshark-dev] need to read three bytes of offset
To: "Developer support list for Wireshark" <wireshark-dev () wireshark org>
Date: Thursday, March 4, 2010, 2:35 PM



On Mar 4, 2010, at 12:00 PM, prashanth s wrote:

> Nopes. But the values that appear in the pcap -  for example,  ba cf need to be interpreted by my parser as ba 
> cf(this is the value,for example, that the company talks about. Hence it may be assumed that the byte order followed 
> by the company is Big Endian.

If you mean that fields in that protocol other than the 3-byte field are big-endian, then...

> So would this mean that the 3 bytes appearing on the pcap also follow the Big Endianness?

...that means that the 3-byte field is probably also big-endian.
___________________________________________________________________________
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