https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4612
--- Comment #2 from Guy Harris <guy@xxxxxxxxxxxx> 2010-04-29 13:27:38 PDT ---
In e-mail, Chris mentioned the byte order.
Some capture file formats (pcap) have a byte order specified by the file. Some
(pcap-ng) can have multiple byte orders, with different byte orders in
different sections. Some have a standard byte order (e.g., many are for
Windows apps, and use little-endian format), and the text formats don't have a
byte order. If we tri-state the byte-order (big/little/not applicable), that
would handle all but pcap-ng, and I'm not sure we yet support mixed-byte-order
pcap-ng files.
In another discussion, the issue of capture files where there was a
snapshot/slice length specified for the capture, but where the slice length
isn't stored in the file; the suggestion in the discussion was that we try to
infer it by looking for packets where the packet length is greater than the
available packet data. We should probably do both and
1) report the stored length only if it's available;
2) report the inferred packet length only if there are packets that were
cut short;
3) report a conflict if both are available but they aren't the same.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
