forked from osmocom/wireshark
94 lines
3.3 KiB
Plaintext
94 lines
3.3 KiB
Plaintext
Wireshark 3.5.0 Release Notes
|
||
|
||
This is an experimental release intended to test new features for
|
||
Wireshark 3.6.
|
||
|
||
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
|
||
|
||
Many improvements have been made. See the “New and Updated Features”
|
||
section below for more details.
|
||
|
||
New and Updated Features
|
||
|
||
The following features are new (or have been significantly updated)
|
||
since version 3.4.0:
|
||
|
||
• TCP conversations now support a completeness criteria, which
|
||
facilitates the identification of TCP streams having any of
|
||
opening or closing handshakes, a payload, in any combination. It
|
||
is accessed with the new tcp.completeness filter.
|
||
|
||
• Protobuf fields that are not serialized on the wire (missing in
|
||
capture files) can now be displayed with default values by
|
||
setting the new 'add_default_value' preference. The default
|
||
values might be explicitly declared in 'proto2' files, or false
|
||
for bools, first value for enums, zero for numeric types.
|
||
|
||
• Wireshark now supports reading Event Tracing for Windows (ETW). A
|
||
new extcap named ETW reader is created that now can open an etl
|
||
file, convert all events in the file to DLT_ETW packets and write
|
||
to a specified FIFO destination. Also, a new packet_etw dissector
|
||
is created to dissect DLT_ETW packets so Wireshark can display
|
||
the DLT_ETW packet header, its message and packet_etw dissector
|
||
calls packet_mbim sub_dissector if its provider matches the MBIM
|
||
provider GUID.
|
||
|
||
New Protocol Support
|
||
|
||
O-RAN fronthaul UC-plane (O-RAN)
|
||
|
||
Updated Protocol Support
|
||
|
||
Too many protocols have been updated to list here.
|
||
|
||
New and Updated Capture File Support
|
||
|
||
Getting Wireshark
|
||
|
||
Wireshark source code and installation packages are available from
|
||
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 download page[1] 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
|
||
|
||
The User’s Guide, manual pages and various other documentation can be
|
||
found at https://www.wireshark.org/docs/
|
||
|
||
Community support is available on Wireshark’sQ&A site[2] and on the
|
||
wireshark-users mailing list. Subscription information and archives
|
||
for all of Wireshark’s mailing lists can be found on the web site[3].
|
||
|
||
Bugs and feature requests can be reported on the issue tracker[4].
|
||
|
||
Frequently Asked Questions
|
||
|
||
A complete FAQ is available on the Wireshark web site[5].
|
||
|
||
Last updated 2020-12-13 09:04:17 UTC
|
||
|
||
References
|
||
|
||
1. https://www.wireshark.org/download.html#thirdparty
|
||
2. https://ask.wireshark.org/
|
||
3. https://www.wireshark.org/lists/
|
||
4. https://gitlab.com/wireshark/wireshark/-/issues
|
||
5. https://www.wireshark.org/faq.html
|