On Nov 9, 2010, at 12:05 PM, Németh Márton wrote:
> OK, that's clear, the byte order of the API structure fields are in "host endian"
> order. The API structures are already saved by Wireshark into file for quite some
> time.
...and tcpdump. Support for capturing on USB on Linux has been in libpcap since at least libpcap 1.0.
When reading a pcap file, or a pcap-ng file section, written on a machine with a byte order opposite from that of the machine reading the file, libpcap and Wireshark's Wiretap library byte-swap most host-byte-order fields into the byte order of the host reading the file; the exceptions are the iso_rec structure and the isochronous descriptors.