Wireshark mailing list archives
Re: usbmon: size of different fields?
From: Guy Harris <guy () alum mit edu>
Date: Tue, 9 Nov 2010 13:23:28 -0800
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. ___________________________________________________________________________ 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
Current thread:
- usbmon: size of different fields? Németh Márton (Nov 08)
- Re: usbmon: size of different fields? Maynard, Chris (Nov 09)
- Re: usbmon: size of different fields? Guy Harris (Nov 09)
- Re: usbmon: size of different fields? Pete Zaitcev (Nov 11)
- Re: usbmon: size of different fields? Németh Márton (Nov 09)
- Re: usbmon: size of different fields? Guy Harris (Nov 09)
- Re: usbmon: size of different fields? Pete Zaitcev (Nov 11)
- Re: usbmon: size of different fields? Guy Harris (Nov 10)
- Re: usbmon: size of different fields? Németh Márton (Nov 09)
- Re: usbmon: size of different fields? Maynard, Chris (Nov 09)