Wireshark-announce: [Wireshark-announce] Wireshark 2.1.0 is now available
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 8 Jun 2016 14:50:20 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I'm proud to announce the release of Wireshark 2.1.0.
This is a semi-experimental release intended to test new features for
Wireshark 2.2.
__________________________________________________________________
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 2.0.0:
* You can now switch between between Capture and File Format
dissection of the current capture file via the View menu in the Qt
GUI.
* You can now show selected packet bytes as ASCII, HTML, Image, ISO
8859-1, Raw, UTF-8, a C array, or YAML.
* You can now use regular expressions in Find Packet and in the
advanced preferences.
* Name resolution for packet capture now supports asynchronous DNS
lookups only. Therefore the "concurrent DNS resolution" preference
has been deprecated and is a no-op. To enable DNS name resolution
some build dependencies must be present (currently c-ares). If that
is not the case DNS name resolution will be disabled (but other
name resolution mechanisms, such as host files, are still
available).
* The byte under the mouse in the Packet Bytes pane is now
highlighted.
* TShark supports exporting PDUs via the -U flag.
* The Windows and OS X installers now come with the "sshdump" and
"ciscodump" extcap interfaces.
* Most dialogs in the Qt UI now save their size and positions.
* The Follow Stream dialog now supports UTF-16.
* The Firewall ACL Rules dialog has returned.
* The Flow (Sequence) Analysis dialog has been improved.
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:
New Protocol Support
Apache Cassandra - CQL version 3.0, Bachmann bluecom Protocol,
Bluetooth Pseudoheader for BR/EDR, CISCO ERSPAN3 Marker, Edge Control
Protocol (ECP), Ericsson IPOS Kernel Packet Header Dissector Added
(IPOS), Extensible Control & Management Protocol (eCMP), FLEXRAY
Protocol dissector added (automotive bus), ISO 8583-1, ISO14443, ITU-T
G.7041/Y.1303 Generic Framing Procedure (GFP), LAT protocol (DECNET),
Metamako trailers, Nokia Intelligent Service Interface (ISI), Open
Mobile Alliance Lightweight Machine to Machine TLV payload Added (LwM2M
TLV), RTI TCP Transport Layer (RTITCP), STANAG 5602 SIMPLE, USB3 Vision
Protocol (USB machine vision cameras), USBIP Protocol, UserLog
Protocol, and Zigbee Protocol Clusters Dissectors Added (Closures
Lighting General Measurement & Sensing HVAC Security & Safety)
Updated Protocol Support
Bluetooth OBEX dissector (btobex) was renamed to Obex Dissector (obex),
allow to DecodeAs it over USB, TCP and UDP.
A preference was added to TCP dissector for handling IPFIX process
information. It has been disabled by default.
New and Updated Capture File Support
and Micropross mplog
New and Updated Capture Interfaces support
Non-empty section placeholder.
Major API Changes
The libwireshark API has undergone some major changes:
* The address macros (e.g., SET_ADDRESS) have been removed. Use the
(lower case) functions of the same names instead.
* "old style" dissector functions (that don't return number of bytes
used) have been replaced in name with the "new style" dissector
functions.
* tvb_get_string and tvb_get_stringz have been replaced with
tvb_get_string_enc and tvb_get_stringz_enc respectively.
__________________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available from
[1]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 [2]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. ([3]Bug 1419)
The BER dissector might infinitely loop. ([4]Bug 1516)
Capture filters aren't applied when capturing from named pipes. ([5]Bug
1814)
Filtering tshark captures with read filters (-R) no longer works.
([6]Bug 2234)
Application crash when changing real-time option. ([7]Bug 4035)
Packet list rows are oversized. ([8]Bug 4357)
Wireshark and TShark will display incorrect delta times in some cases.
([9]Bug 4985)
Wireshark should let you work with multiple capture files. ([10]Bug
10488)
Dell Backup and Recovery (DBAR) makes many Windows applications crash,
including Wireshark. ([11]Bug 12036)
__________________________________________________________________
Getting Help
Community support is available on [12]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 [13]the web site.
Official Wireshark training and certification are available from
[14]Wireshark University.
__________________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [15]Wireshark web site.
__________________________________________________________________
Last updated 2016-06-08 21:31:40 UTC
References
1. https://www.wireshark.org/download.html
2. https://www.wireshark.org/download.html#thirdparty
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12036
12. https://ask.wireshark.org/
13. https://www.wireshark.org/lists/
14. http://www.wiresharktraining.com/
15. https://www.wireshark.org/faq.html
Digests
wireshark-2.1.0.tar.bz2: 32605482 bytes
SHA256(wireshark-2.1.0.tar.bz2)=f73bd7660056c0910c8a89f480f61ab9fe62866eadf1af49e3374da3fe16b4cc
RIPEMD160(wireshark-2.1.0.tar.bz2)=8bb83ba3991c7fe603b2d07c0e4af3fb33e845e7
SHA1(wireshark-2.1.0.tar.bz2)=58c73f622be7febb81ae687eac5885ecfe4c38f0
MD5(wireshark-2.1.0.tar.bz2)=61e1777076fd52253fe6644f757d1ebc
Wireshark-win32-2.1.0.exe: 44373632 bytes
SHA256(Wireshark-win32-2.1.0.exe)=943e03c5606d9e4146d9d0881ec6d3582e551c31a6c28da3e020bb36e6830012
RIPEMD160(Wireshark-win32-2.1.0.exe)=68682658c78b90b65e78e9607db44b356d00e102
SHA1(Wireshark-win32-2.1.0.exe)=efebe846111dd627b9ced3a1c1a74e77030e6ae3
MD5(Wireshark-win32-2.1.0.exe)=ca4a4f796819b05102272f1793892432
Wireshark-win64-2.1.0.exe: 49161192 bytes
SHA256(Wireshark-win64-2.1.0.exe)=6b1c8c3e1020c4f388a0b57ca8a764c0608b729d6a351918f08a29ab6c11d7d3
RIPEMD160(Wireshark-win64-2.1.0.exe)=2a60de09fbd25fdbb3943aea6265248bf98e91a9
SHA1(Wireshark-win64-2.1.0.exe)=d2297c944266c1457332eb5591b3b8ebbe353c40
MD5(Wireshark-win64-2.1.0.exe)=884987337f981cbb23c1b886582ba50e
WiresharkPortable_2.1.0.paf.exe: 45777000 bytes
SHA256(WiresharkPortable_2.1.0.paf.exe)=f2d12c10fceeb9214c8dba51a7e93e85f8bb30ef76ce7e38a94bfaa0d400a7d8
RIPEMD160(WiresharkPortable_2.1.0.paf.exe)=923e38c8171380db6b3f7e8288b9edfdbaed4508
SHA1(WiresharkPortable_2.1.0.paf.exe)=f448d6bc99329a167cc366655729fe428e898a91
MD5(WiresharkPortable_2.1.0.paf.exe)=108255de56a356b786bf37bb0d497825
Wireshark 2.1.0 Intel 64.dmg: 32271748 bytes
SHA256(Wireshark 2.1.0 Intel
64.dmg)=ad3aab836aff0b80cd22ca57754a83e22255a303f50009071baeb66dada3a748
RIPEMD160(Wireshark 2.1.0 Intel
64.dmg)=ff2d8af81cde4714fc59b1af52eb3ecafe10f0f4
SHA1(Wireshark 2.1.0 Intel 64.dmg)=de61703aeb44e0961f2588b29216643725c9d5e1
MD5(Wireshark 2.1.0 Intel 64.dmg)=572c4d8f15d087f513e7e0d64b576f09
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJXWJMcAAoJEIIkSnjm/q7qp/IP/1UDX3Va8MHZKmwnSs97t8+s
6818kxHeiQcMQLFBAm2tt984t0txwI/tT52ufVYQutIqZf2a6OOk4v0yFdD1YdUb
EAp7EGli5xCnusW6J2j5CIvbNZhTsXrfPanN/eRC4JRsbPwoJrOh7hbCbDtec9vI
xBP2+gcePqqwSKXO3fVNOsO8Br7s9MdrWA2ZEvIoydgwv53KlbiOXwvMSDC1LPcu
Iy2RMrvuVuQBVX9flmIokt9QJD+SmytOXaEesFjZGzsgX9cgrllBFBkWVgawvMTP
UGyyx180sR3b4K7PgZbfx/ChLcLzSmzoHV70ralyQShOb3PpA0GXl6607omhxyQA
WIZEnZrjWqY8TCZH2wgW0j6/OhHvtZZ9a+CmjUdUD0eBP+UQIeLfroKOB03GHolX
AJZfXyIWhJE4u5cs6mB8JHV6cNyjqG4t+G5S6e5DdeUckUAS11vJCCqNdFo7+Fzf
QmXIwAnT4rutFKOPLgj2T6u2jFF5ir55xWjqtuttadn8tzB7WG1/0yyQKDNe9a6c
9SBt2FolgSHgzPDNyXPN9CmqQ43Ixkz25KGkX/NvxTFaAyBKxuPB+Efoe9qwDx8Y
HGS9bErxDOg6LpOB26m1TfhqbXVVTiClGjnll4+rof7nfhq4aBX+AIbPRwD3KskS
m+xjet2TwsTfuo7nn52C
=wahD
-----END PGP SIGNATURE-----
- Prev by Date: [Wireshark-announce] Wireshark 1.12.12 is now available
- Previous by thread: [Wireshark-announce] Wireshark 1.12.12 is now available
- Index(es):