osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

For Time Reference frames reset the counter for CulmulativeBytes. 

This makes the CulmulativeBytes field make more sense since if we want
something to be a TimeReference frame it is likely that we also want to
measure BOTH time and number of bytes (==culmulative bytes) until the event we are looking at.

svn path=/trunk/; revision=8956
This commit is contained in:
Ronnie Sahlberg 2003-11-13 08:22:48 +00:00
parent a2e3a35f06
commit cd46db5e4b
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/ethereal.pod
View File

@ -554,6 +554,8 @@ Packets that have been selected as Time Reference packets will always be
displayed in the packet pane. Display filters will not affect or hide these
packets.
If there is a column displayed for "Culmulative Bytes" this counter will
be reset at every Time Reference frame.
=item Edit:Mark Frame

7
file.c
View File

@ -1,7 +1,7 @@
/* file.c
* File I/O routines
*
* $Id: file.c,v 1.321 2003/11/12 18:48:53 gerald Exp $
* $Id: file.c,v 1.322 2003/11/13 08:22:47 sahlberg Exp $
*
* Ethereal - Network traffic analyzer
* By Gerald Combs <gerald@ethereal.com>
@ -804,6 +804,11 @@ add_packet_to_packet_list(frame_data *fdata, capture_file *cf,
/* This frame either passed the display filter list or is marked as
a time reference frame. All time reference frames are displayed
even if they dont pass the display filter */
/* if this was a TIME REF frame we should reset the cul bytes field */
if(edt->pi.fd->flags.ref_time){
cul_bytes = fdata->pkt_len;
fdata->cul_bytes = cul_bytes;
}
/* increase cul_bytes with this packets length */
cul_bytes += fdata->pkt_len;