Guy Harris wrote:
Richard van der Hoff wrote:
One workaround for this is to #define MUST_DO_SELECT, so that
capture_loop_dispatch uses a select() to wait for packets to turn up,
and put a second's timeout on the select() - but i'm not sure how
portable this is likely to be.
It's likely to be quite non-portable...
Yes. I suspected as much.
Anyone got any better ideas?
I'm not sure the display update rate limiting belongs in dumpcap; it
might be better to do it in Wireshark. I.e., have dumpcap send packet
count updates immediately to Wireshark, and have Wireshark decide when
to read the new packets.
The only concern with this would be that dumpcap would presumably then
send a packet count after every packet - which might mean a significant
quantity of data.
--
Richard van der Hoff <richardv@xxxxxxxxxxxxx>
Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
