https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7191
--- Comment #2 from Michael Tüxen <tuexen@xxxxxxxxxxxxx> 2012-04-25 10:58:03 PDT ---
Jasper,
I have commited a fix for the inconsistency in the numbers provided by dumpcap
on the console in
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=42236
So now dumcap reports
[mba:~/Documents/wireshark/trunk] tuexen% ./dumpcap -i lo0 -i en0 -w
test.pcapng
Capturing on lo0 and en0
File: test.pcapng
Packets captured: 98711
Packets received/dropped on interface lo0: 98603/16405 (85.7%)
Packets received/dropped on interface en0: 108/0 (100.0%)
This means: 98711 packets have been written to the test.pcapng file.
>From these 98711 packets, 98603 where received on lo0, 108 on en0. This makes
now sense.
All packets of the en0 interface have been written to the file.
16405 packets which where on the lo0 interface have been dropped. So
98603+16405
packets have been seen on lo0. This is 115008.
What gets written to the Interface Statistics Block: isb_ifrecv 115008,
isb_ifdrop 102.
This means: 115008 packets where received by the libpcap, 102 have been dropped
by the libpcap,
and 16303 have been dropped by dumpcap.
Wireshark shows Numbers in the Interface Statistic Block correctly.
The problem is that the number reported as dropped is misleading.
I'll fix that in a separate fix.
Best regards
Michael
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
