Wireshark-dev: [Wireshark-dev] Wireshark 1.99.3 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 05 Mar 2015 12:13:00 -0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm proud to announce the release of Wireshark 1.99.3.
This is an experimental release intended to test new features for
Wireshark 2.0.
__________________________________________________________________
What is Wireshark?
Wireshark is the world's most popular network protocol analyzer. It is
used for troubleshooting, analysis, development and education.
__________________________________________________________________
What's New
New and Updated Features
The following features are new (or have been significantly updated)
since version 1.99.2:
* Qt port:
+ Several bugs have been fixed.
+ You can now open a packet in a new window.
+ The Bluetooth ATT Server Attributes dialog has been added.
+ The Coloring Rules dialog has been added.
+ Many translations have been updated. Chinese, Italian and
Polish translations are complete.
+ General user interface and usability improvements.
+ Automatic scrolling during capture now works.
+ The related packet indicator has been updated.
The following features are new (or have been significantly updated)
since version 1.99.1:
* Qt port:
+ The welcome screen layout has been updated.
+ The Preferences dialog no longer crashes on Windows.
+ The packet list header menu has been added.
+ Statistics tree plugins are now supported.
+ The window icon is now displayed properly in the Windows
taskbar.
+ A packet list an byte view selection bug has been fixed
([1]Bug 10896)
+ The RTP Streams dialog has been added.
+ The Protocol Hierarchy Statistics dialog has been added.
The following features are new (or have been significantly updated)
since version 1.99.0:
* Qt port:
+ You can now show and hide toolbars and major widgets using the
View menu.
+ You can now set the time display format and precision.
+ The byte view widget is much faster, particularly when
selecting large reassembled packets.
+ The byte view is explorable. Hovering over it highlights the
corresponding field and shows a description in the status bar.
+ An Italian translation has been added.
+ The Summary dialog has been updated and renamed to Capture
File Properties.
+ The VoIP Calls and SIP Flows dialogs have been added.
+ Support for HiDPI / Retina displays has been improved in the
official packages.
* DNS stats: + A new stats tree has been added to the Statistics
menu. Now it is possible to collect stats such as qtype/qclass
distribution, number of resource record per response section, and
stats data (min, max, avg) for values such as query name length or
DNS payload.
* HPFEEDS stats: + A new stats tree has been added to the statistics
menu. Now it is possible to collect stats per channel (messages
count and payload size), and opcode distribution.
* HTTP2 stats: + A new stats tree has been added to the statistics
menu. Now it is possible to collect stats (type distribution).
The following features are new (or have been significantly updated)
since version 1.12.0:
* The I/O Graph in the Gtk+ UI now supports an unlimited number of
data points (up from 100k).
* TShark now resets its state when changing files in ring-buffer
mode.
* Expert Info severities can now be configured.
* Wireshark now supports external capture interfaces. External
capture interfaces can be anything from a tcpdump-over-ssh pipe to
a program that captures from proprietary or non-standard hardware.
This functionality is not available in the Qt UI yet.
* Qt port:
+ The Qt UI is now the default (program name is wireshark).
+ A Polish translation has been added.
+ The Interfaces dialog has been added.
+ The interface list is now updated when interfaces appear or
disappear.
+ The Conversations and Endpoints dialogs have been added.
+ A Japanese translation has been added.
+ It is now possible to manage remote capture interfaces.
+ Windows: taskbar progress support has been added.
+ Most toolbar actions are in place and work.
+ More command line options are now supported
New Protocol Support
(LISP) TCP Control Message, AllJoyn Reliable Datagram Protocol, Android
ADB, Android Logcat text, BGP Monitoring Prototol (BMP), ceph,
corosync/totemnet corosync cluster engine ( lowest
levelencryption/decryption protocol), corosync/totemsrp corosync
cluster engine ( totem single ring protocol), Couchbase, CP "Cooper"
2179, DJI UAV Drone Control Protocol, Dynamic Source Routing (RFC
4728), Elasticsearch, ETSI Card Application Toolkit - Transport
Protocol, Generic Network Virtualization Encapsulation (Geneve), GVSP
GigE Vision (TM) Streaming Protocol, HCrt, HiQnet, IPMI Trace, iSER,
KNXnetIP, MACsec Key Agreement - EAPoL-MKA, MCPE (Minecraft Pocket
Edition), OptoMMP, QNEX6 (QNET), RakNet games library, Remote Shared
Virtual Disk - RSVD, Riemann, S7 Communication, Secure Socket Tunnel
Protocol (SSTP), Shared Memory Communications - RDMA, Stateless
Transport Tunneling, and ZVT Kassenschnittstelle
Updated Protocol Support
Too many protocols have been updated to list here.
New and Updated Capture File Support
Android Logcat text files, Colasoft Capsa files, and Wireshark now
supports nanosecond timestamp resolution in PCAP-NG files.
Major API Changes
The libwireshark API has undergone some major changes:
* The emem framework (including all ep_ and se_ memory allocation
routines) has been completely removed in favour of wmem which is
now fully mature.
* The (long-since-broken) Python bindings support has been removed.
If you want to write dissectors in something other than C, use Lua.
__________________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available from
[2]https://www.wireshark.org/download.html.
Vendor-supplied Packages
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 [3]download page on the Wireshark web site.
__________________________________________________________________
File Locations
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.
__________________________________________________________________
Known Problems
Dumpcap might not quit if Wireshark or TShark crashes. ([4]Bug 1419)
The BER dissector might infinitely loop. ([5]Bug 1516)
Capture filters aren't applied when capturing from named pipes. ([6]Bug
1814)
Filtering tshark captures with read filters (-R) no longer works.
([7]Bug 2234)
Resolving ([8]Bug 9044) reopens ([9]Bug 3528) so that Wireshark no
longer automatically decodes gzip data when following a TCP stream.
Application crash when changing real-time option. ([10]Bug 4035)
Hex pane display issue after startup. ([11]Bug 4056)
Packet list rows are oversized. ([12]Bug 4357)
Wireshark and TShark will display incorrect delta times in some cases.
([13]Bug 4985)
The 64-bit version of Wireshark will leak memory on Windows when the
display depth is set to 16 bits ([14]Bug 9914)
Wireshark should let you work with multiple capture files. ([15]Bug
10488)
__________________________________________________________________
Getting Help
Community support is available on [16]Wireshark's Q&A site and on the
wireshark-users mailing list. Subscription information and archives for
all of Wireshark's mailing lists can be found on [17]the web site.
Official Wireshark training and certification are available from
[18]Wireshark University.
__________________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [19]Wireshark web site.
__________________________________________________________________
Last updated 2015-03-05 18:15:49 UTC
References
1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10896
2. https://www.wireshark.org/download.html
3. https://www.wireshark.org/download.html#thirdparty
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9914
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
16. http://ask.wireshark.org/
17. https://www.wireshark.org/lists/
18. http://www.wiresharktraining.com/
19. https://www.wireshark.org/faq.html
Digests
wireshark-1.99.3.tar.bz2: 29764857 bytes
MD5(wireshark-1.99.3.tar.bz2)=96cc0a3035d063db4dd6d414b8e32fc1
SHA1(wireshark-1.99.3.tar.bz2)=7abd70826396fcbae176c4c4923c4255f6ae4513
RIPEMD160(wireshark-1.99.3.tar.bz2)=3e207b551698ad65722761ff95ece7b805c5bfc6
Wireshark-win32-1.99.3.exe: 35912344 bytes
MD5(Wireshark-win32-1.99.3.exe)=26ae885b78a8c59dc6ca990f40eab667
SHA1(Wireshark-win32-1.99.3.exe)=77fe79f0eb9c2aca7b2b69dce04fe98d364384fe
RIPEMD160(Wireshark-win32-1.99.3.exe)=b87b2931a2e41b1a1c4f64992b8310fea18b1c49
Wireshark-win64-1.99.3.exe: 44192712 bytes
MD5(Wireshark-win64-1.99.3.exe)=54ba3566c927f8d10e3227889a58b06e
SHA1(Wireshark-win64-1.99.3.exe)=01aa1f7eeb0e75f823bb23088a134275ab550167
RIPEMD160(Wireshark-win64-1.99.3.exe)=ac4f605375988efdf81933d02c41f5f2330a11ba
WiresharkPortable_1.99.3.paf.exe: 29566584 bytes
MD5(WiresharkPortable_1.99.3.paf.exe)=9d8dfea03ed6e052fc737f04c05618f2
SHA1(WiresharkPortable_1.99.3.paf.exe)=01abf085b806b45b6718ab06e282ffaaad8f5997
RIPEMD160(WiresharkPortable_1.99.3.paf.exe)=b7b35aad618d34e6e7ce3639a41dafabbbfd9260
Wireshark 1.99.3 Intel 64.dmg: 43265126 bytes
MD5(Wireshark 1.99.3 Intel 64.dmg)=4fa33f385fcf3c5fb65ba596e59e475c
SHA1(Wireshark 1.99.3 Intel 64.dmg)=c798a64a9e5f616bb4c944093f7c3792202c1a0f
RIPEMD160(Wireshark 1.99.3 Intel
64.dmg)=667eb21811c31a84eccb090433b6d74a339f7501
Wireshark 1.99.3 Intel 32.dmg: 33478546 bytes
MD5(Wireshark 1.99.3 Intel 32.dmg)=6f3de1d21da37828d0120f608f6d1184
SHA1(Wireshark 1.99.3 Intel 32.dmg)=6c9c0414e691440003ba387ae19f93246afaee5e
RIPEMD160(Wireshark 1.99.3 Intel
32.dmg)=437d8f164036bd0243bde23ef8313de5ca8fa63d
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlT4uMwACgkQpw8IXSHylJp4LgCfYcf9WqabwAjMhWzjj13k1U3h
xHAAnRrmiv2E/Coz/H+T/SLL/8NCObtX
=ljrL
-----END PGP SIGNATURE-----
- Prev by Date: [Wireshark-dev] Packet editor
- Next by Date: Re: [Wireshark-dev] Packet editor
- Previous by thread: Re: [Wireshark-dev] Packet editor
- Next by thread: [Wireshark-dev] Latest build modifies files?
- Index(es):