1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
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:
• The Windows installers now ship with Npcap 1.31. They previously
shipped with Npcap 1.20.
• 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.
• "Follow DCCP stream" feature to filter for and extract the
contents of DCCP streams.
• Wireshark now supports dissecting the rtp packet with OPUS
payload.
• Importing captures from text files is now also possible based on
regular expressions. By specifying a regex capturing a single
packet including capturing groups for relevant fields a textfile
can be converted to a libcap capture file. Supported data
encodings are plain-hexadecimal, -octal, -binary and base64. Also
the timestamp format now allows the second-fractions to be placed
anywhere in the timestamp and it will be stored with nanosecond
instead of microsecond precision.
• Significant RTP Player redesign and improvements (see Wireshark
User Documentation, Playing VoIP Calls[1] and RTP Player
Window[2])
• RTP Player can play many streams in row
• UI is more responsive
• RTP Player maintains playlist, other tools can add/remove streams
to it
• Every stream can be muted or routed to L/R channel for replay
• Save audio is moved from RTP Analysis to RTP Player. RTP Player
saves what was played. RTP Player can save in multichannel .au or
.wav.
• RTP Player added to menu Telephony>RTP>RTP Player
VoIP dialogs (VoIP Calls, RTP Streams, RTP Analysis, RTP Player, SIP
Flows) are non-modal, can stay opened on background
• Same tools are provided acros all dialogs (Prepare Filter,
Analyse, RTP Player …)
Follow stream is now able to follow SIP call by SIP.Call-ID
New Protocol Support
Kerberos SPAKE, O-RAN fronthaul UC-plane (O-RAN), PDU Transport
Protocol, R09.x (R09), SparkplugB, State Synchronization Protocol (SSyncP),
and UAVCAN\CAN.
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[3] 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’s Q&A site[4] 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[5].
Bugs and feature requests can be reported on the issue tracker[6].
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site[7].
Last updated 2021-05-09 09:05:30 UTC
References
1. https://www.wireshark.org/docs/wsug_html_chunked/ChTelPlayingCalls
.html
2. https://www.wireshark.org/docs/wsug_html_chunked/_rtp.html#ChTelRt
pPlayer
3. https://www.wireshark.org/download.html#thirdparty
4. https://ask.wireshark.org/
5. https://www.wireshark.org/lists/
6. https://gitlab.com/wireshark/wireshark/-/issues
7. https://www.wireshark.org/faq.html
|
