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: [Wireshark-dev] Wrong FCS in 802.11 capture

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


From: Gisle Vanem <gvanem@xxxxxxxxxxxx>
Date: Tue, 07 Apr 2009 07:40:47 +0200

Can anybody verify the attached live capure I did just now?
All the frames in the capture seems to have wrong Frame Check Sequence numbers. The capture was done with latest AirPcap on a Win-XP SP3 box running 
the latest svn version of WireShark. Also verified with tshark.

--gv

Attachment: etherXXXXa04084
Description: Binary data

  • Follow-Ups:
    • [Wireshark-dev] Using port numbers to determine next dissector
      • From: Rayne
    • Re: [Wireshark-dev] Wrong FCS in 802.11 capture
      • From: Gianluca Varenni
  • Prev by Date: Re: [Wireshark-dev] slow startup caused by splash_update?
  • Next by Date: [Wireshark-dev] Using port numbers to determine next dissector
  • Previous by thread: [Wireshark-dev] buildbot failure in Wireshark (release) on Windows-XP-x86
  • Next by thread: [Wireshark-dev] Using port numbers to determine next dissector
  • Index(es):
    • Date
    • Thread

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