2016-11-01 21:35:29 +00:00
|
|
|
|
include::attributes.asciidoc[]
|
2018-02-20 01:13:08 +00:00
|
|
|
|
:stylesheet: ws.css
|
2018-02-25 17:17:14 +00:00
|
|
|
|
:linkcss:
|
2016-11-01 21:35:29 +00:00
|
|
|
|
|
2016-07-16 07:53:37 +00:00
|
|
|
|
= Wireshark {wireshark-version} Release Notes
|
2014-10-02 21:15:05 +00:00
|
|
|
|
// AsciiDoc quick reference: http://powerman.name/doc/asciidoc
|
2018-02-06 20:35:21 +00:00
|
|
|
|
// Asciidoctor Syntax Quick Reference:
|
|
|
|
|
|
// http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
|
2014-04-15 16:31:24 +00:00
|
|
|
|
|
2018-04-03 00:40:20 +00:00
|
|
|
|
This is an experimental release intended to test new features for
|
2019-02-06 19:53:00 +00:00
|
|
|
|
Wireshark 3.2.
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
|
|
|
|
|
== What is Wireshark?
|
|
|
|
|
|
|
2018-02-04 23:15:02 +00:00
|
|
|
|
Wireshark is the world’s most popular network protocol analyzer. It is
|
2013-03-15 01:33:46 +00:00
|
|
|
|
used for troubleshooting, analysis, development and education.
|
|
|
|
|
|
|
2018-02-04 23:15:02 +00:00
|
|
|
|
== What’s New
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
2018-02-16 23:28:29 +00:00
|
|
|
|
Many user interface improvements have been made. See the “New and Updated
|
|
|
|
|
|
Features” section below for more details.
|
2017-09-02 23:42:00 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
// === Bug Fixes
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
// The following bugs have been fixed:
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
2018-05-24 18:35:45 +00:00
|
|
|
|
//* wsbuglink:5000[]
|
|
|
|
|
|
//* wsbuglink:6000[Wireshark bug]
|
|
|
|
|
|
//* cveidlink:2014-2486[]
|
2019-02-06 19:33:12 +00:00
|
|
|
|
//* Wireshark is solely responsible for the decline of shopping malls in your area.
|
2018-03-12 15:49:12 +00:00
|
|
|
|
|
2013-03-15 01:33:46 +00:00
|
|
|
|
=== New and Updated Features
|
|
|
|
|
|
|
2018-12-13 00:39:20 +00:00
|
|
|
|
The following features are new (or have been significantly updated)
|
2019-02-06 19:33:12 +00:00
|
|
|
|
since version 3.0.0:
|
2018-12-13 00:39:20 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
* Watch this space.
|
2018-12-13 00:39:20 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
// === Removed Features and Support
|
2018-05-10 15:53:42 +00:00
|
|
|
|
|
2014-06-06 18:39:55 +00:00
|
|
|
|
//=== Removed Dissectors
|
2014-01-03 09:48:53 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
// === New File Format Decoding Support
|
2018-12-11 23:17:53 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
// [commaize]
|
|
|
|
|
|
// --
|
|
|
|
|
|
// --
|
2014-01-03 09:48:53 +00:00
|
|
|
|
|
2013-03-15 01:33:46 +00:00
|
|
|
|
=== New Protocol Support
|
2016-06-03 16:21:21 +00:00
|
|
|
|
|
Switch from AsciiDoc to Asciidoctor.
Switch the markup text processor for files in the docbook directory from
AsciiDoc to Asciidoctor. Asciidoctor has several useful features (such
as direct PDF output) and is actively developed. It's written in Ruby
but that dependency can be sidestepped with AsciidoctorJ, a
self-contained bundle that only depends on the JRE.
The current toolchain targets require Python, AsciiDoc, DocBook XML,
DocBook XSL, Java, FOP, xsltproc, lynx, and the HTMLHelp compiler:
HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL
Chunked HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL
PDF: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → FOP
HTMLHelp: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → HHC
This change removes the AsciiDoc and FOP requirements and adds either
AsciidoctorJ or Asciidoctor + Ruby:
HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL
Chunked HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL
PDF: Asciidoctor
HTMLHelp: Asciidoctor → DocBook XML → xsltproc + DocBook XSL → HHC
Ideally we could generate all of these using AsciidoctorJ, Java, and
lynx. Unfortunately we're not there yet.
The release notes depend on several macros (ws-buglink, ws-salink,
cve-idlink, sort-and-group). Add Asciidoctor (Ruby) equivalents.
Remove the BUILD_xxx_GUIDES CMake options and add various output targets
automatically. This means that you have to build the various documentation
targets explicitly.
Change-Id: I31930677a656b99b1c6839bb6c33a13db951eb9a
Reviewed-on: https://code.wireshark.org/review/25668
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2017-10-19 22:03:55 +00:00
|
|
|
|
// Add one protocol per line between the -- delimiters.
|
|
|
|
|
|
[commaize]
|
|
|
|
|
|
--
|
2018-05-28 13:16:35 +00:00
|
|
|
|
--
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
|
|
|
|
|
=== Updated Protocol Support
|
|
|
|
|
|
|
2016-08-16 14:50:37 +00:00
|
|
|
|
Too many protocols have been updated to list here.
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
|
|
|
|
|
=== New and Updated Capture File Support
|
|
|
|
|
|
|
2018-01-06 01:02:57 +00:00
|
|
|
|
//_Non-empty section placeholder._
|
2016-06-08 16:15:24 +00:00
|
|
|
|
// Add one file type per line between the --sort-and-group-- delimiters.
|
Switch from AsciiDoc to Asciidoctor.
Switch the markup text processor for files in the docbook directory from
AsciiDoc to Asciidoctor. Asciidoctor has several useful features (such
as direct PDF output) and is actively developed. It's written in Ruby
but that dependency can be sidestepped with AsciidoctorJ, a
self-contained bundle that only depends on the JRE.
The current toolchain targets require Python, AsciiDoc, DocBook XML,
DocBook XSL, Java, FOP, xsltproc, lynx, and the HTMLHelp compiler:
HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL
Chunked HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL
PDF: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → FOP
HTMLHelp: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → HHC
This change removes the AsciiDoc and FOP requirements and adds either
AsciidoctorJ or Asciidoctor + Ruby:
HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL
Chunked HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL
PDF: Asciidoctor
HTMLHelp: Asciidoctor → DocBook XML → xsltproc + DocBook XSL → HHC
Ideally we could generate all of these using AsciidoctorJ, Java, and
lynx. Unfortunately we're not there yet.
The release notes depend on several macros (ws-buglink, ws-salink,
cve-idlink, sort-and-group). Add Asciidoctor (Ruby) equivalents.
Remove the BUILD_xxx_GUIDES CMake options and add various output targets
automatically. This means that you have to build the various documentation
targets explicitly.
Change-Id: I31930677a656b99b1c6839bb6c33a13db951eb9a
Reviewed-on: https://code.wireshark.org/review/25668
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2017-10-19 22:03:55 +00:00
|
|
|
|
[commaize]
|
2018-08-27 15:17:32 +00:00
|
|
|
|
--
|
|
|
|
|
|
--
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
// === New and Updated Capture Interfaces support
|
2015-04-08 14:09:03 +00:00
|
|
|
|
|
2018-01-06 01:02:57 +00:00
|
|
|
|
//_Non-empty section placeholder._
|
2018-10-01 17:20:38 +00:00
|
|
|
|
|
2019-02-06 19:33:12 +00:00
|
|
|
|
// === Major API Changes
|
2014-02-22 19:16:44 +00:00
|
|
|
|
|
2013-03-15 01:33:46 +00:00
|
|
|
|
== Getting Wireshark
|
|
|
|
|
|
|
|
|
|
|
|
Wireshark source code and installation packages are available from
|
2014-09-17 00:15:56 +00:00
|
|
|
|
https://www.wireshark.org/download.html.
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
|
|
|
|
|
=== 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
|
2014-09-17 00:15:56 +00:00
|
|
|
|
on the https://www.wireshark.org/download.html#thirdparty[download page]
|
2013-03-15 01:33:46 +00:00
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
== Getting Help
|
|
|
|
|
|
|
2018-08-09 15:43:47 +00:00
|
|
|
|
The User’s Guide, manual pages and various other documentation can be
|
|
|
|
|
|
found at https://www.wireshark.org/docs/
|
|
|
|
|
|
|
2018-02-04 23:15:02 +00:00
|
|
|
|
Community support is available on https://ask.wireshark.org/[Wireshark’s
|
2013-03-15 01:33:46 +00:00
|
|
|
|
Q&A site] and on the wireshark-users mailing list. Subscription
|
2018-02-04 23:15:02 +00:00
|
|
|
|
information and archives for all of Wireshark’s mailing lists can be
|
2014-09-17 00:15:56 +00:00
|
|
|
|
found on https://www.wireshark.org/lists/[the web site].
|
2013-03-15 01:33:46 +00:00
|
|
|
|
|
2018-08-09 15:43:47 +00:00
|
|
|
|
Bugs and feature requests can be reported on
|
|
|
|
|
|
https://bugs.wireshark.org/[the bug tracker].
|
|
|
|
|
|
|
2013-03-15 01:33:46 +00:00
|
|
|
|
Official Wireshark training and certification are available from
|
|
|
|
|
|
http://www.wiresharktraining.com/[Wireshark University].
|
|
|
|
|
|
|
|
|
|
|
|
== Frequently Asked Questions
|
|
|
|
|
|
|
|
|
|
|
|
A complete FAQ is available on the
|
2014-09-17 00:15:56 +00:00
|
|
|
|
https://www.wireshark.org/faq.html[Wireshark web site].
|