I'm getting a strange error running the following Tshark command in Windows Command Prompt: tshark -q -r capture.cap -t ad -z io,stat,10,ip.src==213.248.117.35 > output.txt Towards the end of the capture I am getting a huge number of bytes but no packets.
When I run the same graph in Wireshark I do not have that problem. Can anyone see my problem? asked 30 Nov '12, 03:45 chazzquire edited 30 Nov '12, 04:20 Kurt Knochner ♦ showing 5 of 9 show 4 more comments |
One Answer:
O.K. so, it looks like a bug. Can you please:
Regards answered 30 Nov '12, 05:44 Kurt Knochner ♦ edited 30 Nov '12, 05:45 Ok, it's not working in 1.9 either so i'll report it. The "-t ad" addition you gave me yesterday doesn't work in 1.6. Do you know any other way that I can show date and time? (30 Nov '12, 05:54) chazzquire
Yes, I've seen that in the meantime. I believe that has been added after 1.6.
Only by rewriting the output of tshark with a script. Get the date/time of the first frame and then add the seconds of the tshark output to that date/time. Perl and Date::Calc may help. UPDATE: Or, run the io stats with 1.6 and 1.8 and take the date/time stamps from the 1.8 output and the data from the 1.6 output. (30 Nov '12, 06:14) Kurt Knochner ♦ |
what is your tshark version (tshark -v)?
1.8.3 Thanks,
O.k. at the first glance, it looks like a bug in thsark io stats.
I would prefer not to upload the capture. It is a large file size (almost 1GB) which was captured over 1 hour whilst streaming video. I'll try creating a smaller capture to see if that helps.
What is you OS version?
I've no tried this with 200MB files and I'm having the same problem.
Windows 7 Professional
can you further reduce the file (half, half, half) to see, if there is any size related issue?
I've downgraded to 1.6.x and this problem is no longer occurring.