Wireshark

  • Riverbed Technology
  • WinPcap
SHARKFEST '13 - Wireshark Developer and User Conference - June 16-19, 2013 - UC Berkeley
  • 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-users: Re: [Wireshark-users] Tshark shows packet loss while tcpdump doesn't! - Why?

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


From: Jakub Zawadzki <darkjames@xxxxxxxxxxxxxxxx>
Date: Wed, 2 Sep 2009 22:32:25 +0200

On Wed, Sep 02, 2009 at 10:02:00PM +0200, H Aslam wrote:
> While running "top" on the linux machine 50% of the processor is occupied.
> So the processor doesn't seem to get overloaded.

If you have 2 CPU (or cores) it might mean that 1 CPU has 100% usage.

Cheers

  • References:
    • Re: [Wireshark-users] Tshark shows packet loss while tcpdump doesn't! - Why?
      • From: H Aslam
  • Prev by Date: Re: [Wireshark-users] Tshark shows packet loss while tcpdump doesn't! - Why?
  • Next by Date: Re: [Wireshark-users] Tshark -R option
  • Previous by thread: Re: [Wireshark-users] Tshark shows packet loss while tcpdump doesn't! - Why?
  • Next by thread: [Wireshark-users] CACE TurboCap / dropping frames / really?
  • Index(es):
    • Date
    • Thread

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