Wireshark-bugs: [Wireshark-bugs] [Bug 1850] tshark IO statistics output only includes offset tim
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 10 Dec 2012 22:12:25 +0000

Comment # 3 on bug 1850 from 
(In reply to comment #2)
>----
>$ tshark -z io,stat,1 -t ad -r /tmp/out.pcap
>Interval:
> 1.000 secs
>Column #0:
>                |   Column #0
>Time            |frames|
> bytes
>000.000-001.000       2       240
>001.000-002.000       0         0
> ----

Which version of TShark are you using?  On both v1.8.4 and SVN with

$ tshark -z io,stat,2 -t ad -r /tmp/out.pcap

I get an output of:

=========================================
| IO Statistics                         |
|                                       |
| Interval size: 2 secs                 |
| Col 1: Frames and bytes               |
|---------------------------------------|
|                     |1                |
| Date and time       | Frames |  Bytes |
|---------------------------------------|
| 2012-12-05 16:24:59 |     72 |  30223 |
| 2012-12-05 16:25:01 |     30 |   6672 |


It doesn't have the "time range" you mentioned in comment #0, but it does have
a real "absolute time".  What I don't like about your "time range" suggestion,
is the difficulty of handling "rollover" when an (uneven) interval passes over
seconds/minutes/hours.  That's why I made the suggestion of listing both
"absolute start" and "absolute end" of the interval.  I would think something
like this:

| 2012-12-05 16:24:59 <> 2012-12-05 16:25:01 |     72 |  30223 |


I'm willing to work on fixing this, but I want to know how different the
current SVN functionality is from your desired functionality.

You are receiving this mail because:
  • You are the assignee for the bug.
  • You are watching all bug changes.