Wireshark-users: [Wireshark-users] Wireshark 2.0.0rc2 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Fri, 30 Oct 2015 14:51:58 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm proud to announce the release of Wireshark 2.0.0rc2.
This is the second release candidate 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
Wireshark 2.0 features a new user interface which should provide a
smoother, faster user experience.
New and Updated Features
The following features are new (or have been significantly updated)
since version 2.0.0rc1:
* For new installations on UN*X, the directory for user preferences
is $HOME/.config/wireshark rather than $HOME/.wireshark. If that
directory is absent, preferences will still be found and stored
under $HOME/.wireshark.
* Qt port:
+ The SIP Statistics dialog has been added.
+ You can now create filter expressions from the display filter
toolbar.
+ Bugs in the UAT prefererences dialog has been fixed.
* Several dissector and Qt UI crash bugs have been fixed.
* Problems with the Mac OS X application bundle have been fixed.
The following features are new (or have been significantly updated)
since version 1.99.9:
* Qt port:
+ The LTE RLC Graph dialog has been added.
+ The LTE MAC Statistics dialog has been added.
+ The LTE RLC Statistics dialog has been added.
+ The IAX2 Analysis dialog has been added.
+ The Conversation Hash Tables dialog has been added.
+ The Dissector Tables dialog has been added.
+ The Supported Protocols dialog has been added.
+ You can now zoom the I/O and TCP Stream graph X and Y axes
independently.
+ The RTP Player dialog has been added.
+ Several memory leaks have been fixed.
The following features are new (or have been significantly updated)
since version 1.99.8:
* Qt port:
+ The MTP3 statistics and summary dialogs have been added.
+ The WAP-WSP statistics dialog has been added.
+ The UDP multicast statistics dialog has been added.
+ The WLAN statistics dialog has been added.
+ The display filter macros dialog has been added.
+ The capture file properties dialog now includes packet
comments.
+ Many more statistics dialogs can be opened from the command
line via -z ....
+ Most dialogs now have a cancellable progress bar.
+ Many packet list and packet detail context menus items have
been added.
+ Lua plugins can be reloaded from the Analyze menu.
+ Many bug fixes and improvements.
The following features are new (or have been significantly updated)
since version 1.99.7:
* Qt port:
+ The Enabled Protocols dialog has been added.
+ Many statistics dialogs have been added, including Service
response time, DHCP/BOOTP, and ANSI.
+ The RTP Analysis dialog has been added.
+ Lua dialog support has been added.
+ You can now manually resolve addresses.
+ The Resolved Addresses dialog has been added.
+ The packet list scrollbar now has a minimap.
+ The capture interfaces dialog has been updated.
+ You can now colorize conversations.
+ Welcome screen behavior has been improved.
+ Plugin support has been improved.
+ Many dialogs should now more correctly minimize and maximize.
+ The reload button has been added back to the toolbar.
+ The "Decode As" dialog no longer saves decoding behavior.
+ You can now stop loading large capture files.
+ The Bluetooth HCI Summary has been added.
The following features are new (or have been significantly updated)
since version 1.99.6:
* Qt port:
+ The Bluetooth Devices dialog has been added.
+ The wireless toolbar has been added.
+ Opening files via drag and drop is now supported.
+ The Capture Filter and Display Filter dialogs have been added.
+ The Display Filter Expression dialog has been added.
+ Conversation Filter menu items have been added.
+ You can change protocol preferences by right clicking on the
packet list and details.
The following features are new (or have been significantly updated)
since version 1.99.4 and 1.99.5:
* Qt port:
+ Capture restarts are now supported.
+ Menu items for plugins are now supported.
+ Extcap interfaces are now supported.
+ The Expert Information dialog has been added.
+ Display and capture filter completion is now supported.
+ Many bugs have been fixed.
+ Translations have been updated.
The following features are new (or have been significantly updated)
since version 1.99.3:
* Qt port:
+ Several interface bugs have been fixed.
+ Translations have been updated.
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 File Format Decoding Support
Wireshark is able to display the format of some types of files (rather
than displaying the contents of those files). This is useful when
you're curious about, or debugging, a file and its format. To open a
capture file (such as PCAP) in this mode specify "MIME Files Format" as
the file's format in the Open File dialog.
New files that Wireshark can open in this mode include:
BTSNOOP, PCAP, and PCAPNG
New Protocol Support
Aeron, AllJoyn Reliable Datagram Protocol, Android Debug Bridge,
Android Debug Bridge Service, Android Logcat text, Apache Tribes
Heartbeat, APT-X Codec, B.A.T.M.A.N. GW, B.A.T.M.A.N. Vis, BGP
Monitoring Prototol (BMP), Bluetooth Broadcom HCI, Bluetooth GATT
Attributes (many), Bluetooth OBEX Applications (many), BSSAP2, C15 Call
History Protocol (C15ch) and others, Celerra VNX, Ceph, Chargen,
Classical IP, Concise Binary Object Representation (CBOR) (RFC 7049),
Corosync Totem Single Ring Protocol, Corosync Totemnet, Couchbase, CP
"Cooper" 2179, CSN.1, dCache, DJI UAV Drone Control Protocol, Dynamic
Source Routing (RFC 4728), Elasticsearch, ETSI Card Application Toolkit
- Transport Protocol, eXpressive Internet Protocol (XIP), GDB Remote
Serial Protocol, Generic Network Virtualization Encapsulation (Geneve),
Geospatial and Imagery Access Service (GIAS), Gias Dissector Using GIOP
API, GPRS Tunneling Protocol Prim, GVSP GigE Vision (TM) Streaming
Protocol, H.225 RAS, Harman HiQnet, HCrt, Hotline Command-Response
Transaction Protocol, IEEE 802.11 radio information, IP Detail Record
(IPDR), IPMI Trace, iSER, KNXnetIP, Link Aggregation Control Protocol,
Link Aggregation Marker Protocol, Link Layer Topology Discovery,
Link-local Multicast Name Resolution, LISP TCP Control Message,
Locator/ID Separation Protocol (Reliable Transport), MACsec Key
Agreement - EAPoL-MKA, MCPE (Minecraft Pocket Edition), Message Queuing
Telemetry Transport For Sensor Networks (MQTT-SN), Minecraft Pocket
Edition, MQ Telemetry Transport Protocol for Sensor Networks, Multicast
Domain Name Service (mDNS), Neighborhood Watch Protocol (NWP), Network
File System over Remote Direct Memory Access (NFSoRDMA), OAMPDU, OCFS2,
OptoMMP, Organization Specific Slow Protocol (OSSP), Packet Cable
Lawful Intercept (8 byte CCCID), Packet Cable Lawful Intercept
(timestamp), Packet Cable Lawful Intercept (timestamp case ID),
PacketCable MTA FQDN, Performance Co-Pilot Proxy, QNEX6 (QNET), RakNet
games library, Remote Shared Virtual Disk (RSVD), Riemann, RPC over
RDMA (RPCoRDMA), S7 Communication, Secure Socket Tunnel Protocol
(SSTP), Shared Memory Communications - RDMA (SMCR), Stateless Transport
Tunneling, TCP based Robot Operating System protocol (TCPROS), Thrift,
Time Division Multiplexing over Packet Network (TDMoP), Video Services
over IP (VSIP), Windows Search Protocol (MS-WSP), XIP Serval, ZigBee
ZCL (many), and ZVT Kassenschnittstelle
Updated Protocol Support
Too many protocols have been updated to list here.
New and Updated Capture File Support
3GPP TS 32.423 Trace, Android Logcat text files, Colasoft Capsa files,
Netscaler 3.5, and Symbian OS BTSNOOP File Format
Additionally, Wireshark now supports nanosecond timestamp resolution in
PCAP-NG files.
New and Updated Capture Interfaces support
Androiddump support now provides interfaces to capture (Logcat,
Bluetooth and WiFi) from connected Android devices.
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.
* Plugins can now create GUI menu items.
* Heuristic dissectors can now be globally enabled/disabled so
heur_dissector_add() has a few more parameters to make that
possible
* proto_tree_add_text has been removed.
* tvb_length() has been removed in favor of tvb_reported_length() and
tvb_captured_length().
* The API for RPC-based dissectors has changed significantly: the
procedure dissectors no longer take an offset, void-argument
procedures now need to be declared with a function (use
dissect_rpc_void()), and rpc_init_prog() now handles procedure
registration too (it takes additional arguments to handle this;
rpc_init_proc_table() was removed).
__________________________________________________________________
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-10-30 18:40:28 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. https://ask.wireshark.org/
17. https://www.wireshark.org/lists/
18. http://www.wiresharktraining.com/
19. https://www.wireshark.org/faq.html
Digests
wireshark-2.0.0rc2.tar.bz2: 30838572 bytes
SHA256(wireshark-2.0.0rc2.tar.bz2)=b1d2139bd1e1b008337546059beece59e24387e7b96c3d691203f0ce1881b6c8
RIPEMD160(wireshark-2.0.0rc2.tar.bz2)=907eefeae0519986d7d62a288fac3568efda020e
SHA1(wireshark-2.0.0rc2.tar.bz2)=3bef75cd106dbf6fba8529394202b90cfcc9f5b2
MD5(wireshark-2.0.0rc2.tar.bz2)=e533e26ae9372b3d58c7d54eddd2ef1e
Wireshark-win32-2.0.0rc2.exe: 37859672 bytes
SHA256(Wireshark-win32-2.0.0rc2.exe)=bf5a9c57b3313f9bc98b57d403ddaaa1a79ee5ab4630acd01cb0af3a61dfa3f2
RIPEMD160(Wireshark-win32-2.0.0rc2.exe)=c15397f1d114e5ea39d1b7e92d353ea506e9e3a5
SHA1(Wireshark-win32-2.0.0rc2.exe)=590eb3d0f84bc93dc94d160f455685830a115d58
MD5(Wireshark-win32-2.0.0rc2.exe)=35623c129b6565a84f3dae7e24feb530
Wireshark-win64-2.0.0rc2.exe: 40706272 bytes
SHA256(Wireshark-win64-2.0.0rc2.exe)=a1c9e8a4bd6a1b41232f02ef218147e931c7b3397f94bb84ef9e3cc9c60b8508
RIPEMD160(Wireshark-win64-2.0.0rc2.exe)=dfc60a2f242da2a9efdf17af611ae99d2b7061c0
SHA1(Wireshark-win64-2.0.0rc2.exe)=73abc28e3c9c62ff861a39862988fcfa26c07379
MD5(Wireshark-win64-2.0.0rc2.exe)=1c349591a7f35cfbac00ceea8520a21c
WiresharkPortable_2.0.0rc2.paf.exe: 42572968 bytes
SHA256(WiresharkPortable_2.0.0rc2.paf.exe)=b4ab03445e9a24806bae70749b86a56f9cce080fc0bd773a160a22af000ab47c
RIPEMD160(WiresharkPortable_2.0.0rc2.paf.exe)=a53fb031eccce0fcac97555fe1cc3bfba46622f0
SHA1(WiresharkPortable_2.0.0rc2.paf.exe)=4ebfeddb7de24bff970f65facf5068fdbfa84168
MD5(WiresharkPortable_2.0.0rc2.paf.exe)=23a89143f8e30c5071d0242afddc72bf
Wireshark 2.0.0rc2 Intel 64.dmg: 31314685 bytes
SHA256(Wireshark 2.0.0rc2 Intel 64.dmg)=e356f2b8f2aca4e57517e6e455d9e1d816ca1af0ba4c5be089f1defa63c769b4
RIPEMD160(Wireshark 2.0.0rc2 Intel 64.dmg)=6c385b3592eb13de27a606943b70de3c9ece342a
SHA1(Wireshark 2.0.0rc2 Intel 64.dmg)=84cabc6b31d33980e0165348a06d8a4f86022967
MD5(Wireshark 2.0.0rc2 Intel 64.dmg)=b4c8ec46e477489c5ebcc9ec3b2228c8
Wireshark 2.0.0rc2 Intel 32.dmg: 32212515 bytes
SHA256(Wireshark 2.0.0rc2 Intel 32.dmg)=ddb547cc0fc284022bb6d40c82e862c09586d5c3f11374219bf23d2532b6068e
RIPEMD160(Wireshark 2.0.0rc2 Intel 32.dmg)=006dc639dd2cc38dd2b93b84f0178186011d7a9b
SHA1(Wireshark 2.0.0rc2 Intel 32.dmg)=b7746328ec333c286dcc6960e1afdd2002d08be9
MD5(Wireshark 2.0.0rc2 Intel 32.dmg)=85ecf7a4a2bf10824cdcaec66664c987
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlYz5n4ACgkQpw8IXSHylJpknACcDz9Foav1tyqbvFRMQdNfCCiu
pf4AnRww33dYknkwIP0ir/ZV+Zaaoh5u
=A5rg
-----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] Multiple traces
- Previous by thread: Re: [Wireshark-users] Multiple traces
- Index(es):