Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Problems with the newly modified and compiled wpcap.dll

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 2 Oct 2007 17:20:13 -0700


On Sep 29, 2007, at 2:06 AM, Varuna De Silva wrote:

In capture->interfaces list displays my device along with the others,
but in the "packets" and "packets/s" column, for all the interfaces listed it shows some very high "unrealistic " values such as 277314 for packets
and extremely high value for packets/s.

Have you implemented an xxx_stats routine that returns the correct packet counts?

And when I press the start button, the program, Hangs up.

Perhaps your xxx_read routine is blocked waiting for a 3968-byte buffer full of data to arrive, even though some data has arrived? See my mail to tcpdump-workers on that.

  • Prev by Date: Re: [Wireshark-dev] Alternative to USBPcap and Possibility of
  • Next by Date: Re: [Wireshark-dev] Alternative to USBPcap and Possibility of
  • Previous by thread: Re: [Wireshark-dev] [Wireshark-commits] rev 23038: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-dcerpc-fldb.c packet-fcct.c packet-fcdns.c packet-fcels.c packet-fcip.c packet-fr.c packet-ftam.c
  • Next by thread: [Wireshark-dev] Two new timestamp columns
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation