Table of Contents
Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development, and education.
The following vulnerabilities have been fixed. See the security advisory for details and a workaround.
The following bugs have been fixed:
Window "capture->Interfaces" cannot be closed. (Bug 1740)
Slow response when using Expert Info Composite. (Bug 2504)
tshark-1.0.2 (dumpcap) signal abort core saved. (Bug 2767)
Crash when applying a display filter. (Bug 3361)
Propagate interface Comment field to the Capture... Interfaces dialogue box. (Bug 3414)
Crash when searching for Time Reference. (Bug 3429)
Wireshark doesn't interpret "adsl" interface in snoop output of Juniper ScreenOS. (Bug 3469)
Wireshark start-up very slow when X forwarding over ssh. (Bug 3483)
Wireshark crashes while reading capture file. (Bug 3489)
Windows build with ADNS fails because some ADNS files are missing. (Bug 3499)
Field wlan_mgt.fixed.delba.param.initiator is indicated by wrong bit of wlan_mgt.fixed.delba.param. (Bug 3505)
Edonkey bug in dissecting UDP Get Gerver Info packets. (Bug 3509)
The Lucent/Ascend file parser could go into an infinite loop. (Bug 3535)
Wireshark crashes when range_string is the data type. (Bug 3536)
FF Protocol "FMS Initiate - Version OD Calling" field packet data not unpacked properly. (Bug 3694)
Wireshark source code and installation packages are available from the download page on the main web site.
Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the download page on the Wireshark web site.
Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About->Folders to find the default locations on your system.
Wireshark may appear offscreen on multi-monitor Windows systems. (Bug 553)
Wireshark might make your system disassociate from a wireless network on OS X. (Bug 1315)
Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419)
The BER dissector might infinitely loop. (Bug 1516)
Wireshark can't dynamically update the packet list. This means that host name resolutions above a certain response time threshold won't show up in the packet list. (Bug 1605)
Capture filters aren't applied when capturing from named pipes. (Bug 1814)
Wireshark might freeze when reading from a pipe. (Bug 2082)
Capturing from named pipes might be delayed on Windows. (Bug 2200)
Filtering tshark captures with display filters (-R) no longer works. (Bug 2234)
Community support is available on the wireshark-users mailing list. Subscription information and archives for all of Wireshark's mailing lists can be found on the web site.
Commercial support and development services are available from CACE Technologies.
A complete FAQ is available on the Wireshark web site.
Riverbed is Wireshark's primary sponsor and provides our funding. They also make great products.
Packet Analysis Made Easy
- Visually rich, powerful LAN analyzer
- Quickly access very large pcap files
- Professional, customizable reports
- Advanced triggers and alerts
- Fully integrated with Wireshark
