Ethereal-dev: Re: [Ethereal-dev] ETHEREAL bug in handling TR1 file format

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Harris <gharris@xxxxxxxxx>
Date: Sun, 29 Jun 2003 17:44:10 -0700
On Fri, Jun 27, 2003 at 02:03:32AM -0700, Guy Harris wrote:
> Something that would handle
> 
> 	1) LANalyzer files in which the "length of the packet in
> 	   bytes" is the length including, presumably, the FCS, and in
> 	   which the "length of packet slice in bytes" never includes
> 	   the FCS (*ALL* the LANalyzer captures I've seen are like that -
> 	   have you seen any that aren't?), so that "rx_frm_len" is
> 	   always greater than "rx_frm_sln" by at least 4
> 
> and
> 
> 	2) files from NETMON *if* no slicing is done, so that
> 	   "rx_frm_len" and "rx_frm_sln" are the same
> 
> whould be to make the "bytes on wire" value be the maximum of
> "rx_frm_len - 4" and "rx_frm_sln", so that:
> 
> 	1) in the first case, "rx_frm_len - 4" will be >= "rx_frm_sln",
> 	   and Ethereal will work as it does now;
> 
> 	2) in the second case, "rx_frm_len - 4" will be < "rx_frm_sln",
> 	   and both lengths will be reported as "rx_frm_sln".

I've checked that in.