Re: need to read three bytes of offset

[prashanth s <prbanglore () gmail com>]

Hi Harris,

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.
So would this mean that the 3 bytes appearing on the pcap also follow the
Big Endianness?

Regards,
Prashanth

On Thu, Mar 4, 2010 at 11:42 PM, Guy Harris <guy () alum mit edu> wrote:

> On Mar 4, 2010, at 10:08 AM, prashanth joshi wrote:
>
> > Thanks Harris for the response. In our case the functional spec of the
> company says that the offset is a three byte field.
>
> Does it say whether it's in network byte order or little-endian byte order?
> ___________________________________________________________________________
> 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