2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
9 -Use this section to encode all document information
15 <!ENTITY WiresharkCurrentVersion "1.5.0">
20 <title>Wireshark &WiresharkCurrentVersion; Release Notes</title>
22 <section id="WhatIs"><title>What is Wireshark?</title>
24 Wireshark is the world's most popular network protocol analyzer. It
25 is used for troubleshooting, analysis, development and education.
29 <section id="WhatsNew"><title>What's New</title>
30 <section id="BugFixes"><title>Bug Fixes</title>
34 The following bugs have been fixed:
39 Wireshark is unresponsive when capturing from named pipes on Windows.
40 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1759">Bug
50 <section id="NewFeatures"><title>New and Updated Features</title>
52 The following features are new (or have been significantly updated)
59 The packet list internals have been rewritten and are now more
66 Columns are easier to use. You can add a protocol field as a column
67 by right-clicking on its packet detail item, and you can adjust
68 some column preferences by right-clicking the column header.
74 Preliminary Python scripting support has been added.
80 Many memory leaks have been fixed.
86 Wireshark no longer supports Windows 2000. Please use
87 Wireshark 1.2 or 1.0 on those systems.
93 Packets can now be ignored (excluded from dissection), similar to
94 the way they can be marked.
100 Manual IP address resolution is now supported.
106 Columns with seconds can now be displayed as hours, minutes and
113 You can now set the capture buffer size on UNIX and Linux if you have
114 libpcap 1.0.0 or greater.
120 TShark no longer needs elevated privileges on UNIX or Linux to list
121 interfaces. Only dumpcap requires privileges now.
127 Wireshark and TShark can enable 802.11 monitor mode directly if you
128 have libpcap 1.0.0 or greater.
134 Play the RTP stream directly from the RTP Analysis.
140 Capinfos and editcap now respectively support time order checking
150 <section id="NewProtocols"><title>New Protocol Support</title>
156 <section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>
161 <section id="NewCapture"><title>New and Updated Capture File Support</title>
169 <section id="GettingWireshark"><title>Getting Wireshark</title>
171 Wireshark source code and installation packages are available from
172 <ulink url="http://www.wireshark.org/download.html">http://www.wireshark.org/download.html</ulink>.
175 <section id="VendorPackages"><title>Vendor-supplied Packages</title>
177 Most Linux and Unix vendors supply their own Wireshark packages.
178 You can usually install or upgrade Wireshark using the package management
179 system specific to that platform. A list of third-party packages
181 <ulink url="http://www.wireshark.org/download.html#thirdparty">download page</ulink>
182 on the Wireshark web site.
188 <!-- XXX needs to be written
189 <section id="RemovingWireshark"><title>Removing Wireshark</title>
195 <section id="FileLocations"><title>File Locations</title>
197 Wireshark and TShark look in several different locations for
198 preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
199 These locations vary from platform to platform. You can use
200 About->Folders to find the default locations on your system.
204 <section id="KnownProblems"><title>Known Problems</title>
207 Wireshark may appear offscreen on multi-monitor Windows systems.
208 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
213 Wireshark might make your system disassociate from a wireless network
215 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
220 Dumpcap might not quit if Wireshark or TShark crashes.
221 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
226 The BER dissector might infinitely loop.
227 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516">Bug
232 Capture filters aren't applied when capturing from named pipes.
233 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814">Bug
238 Filtering tshark captures with display filters (-R) no longer works.
239 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234">Bug
244 The 64-bit Windows installer does not ship with the same libraries as the
246 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3610">Bug
251 Application crash when changing real-time option.
252 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035">Bug
257 Hex pane display issue after startup.
258 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056">Bug
263 Crash when sorting column while capturing.
264 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4273">Bug
269 Packet list rows are oversized.
270 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357">Bug
275 Summary pane selected frame highlighting not maintained.
276 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445">Bug
282 <section id="GettingHelp"><title>Getting Help</title>
284 Community support is available on the wireshark-users mailing list.
285 Subscription information and archives for all of Wireshark's mailing
286 lists can be found on <ulink url="http://www.wireshark.org/lists/">the
290 Commercial support is available from
291 <ulink url="http://www.cacetech.com/products/sharknet.html">CACE Technologies</ulink>.
294 Training is available from
295 <ulink url="http://www.wiresharktraining.com/">Wireshark University</ulink>.
299 <section id="FAQ"><title>Frequently Asked Questions</title>
301 A complete FAQ is available on the
302 <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.