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
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
|
Wireshark 3.5.1 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.55.
• A 64-bit Windows PortableApps package is now available.
• A macOS Arm 64 (Apple Silicon) package is now available.
• 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 libpcap 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.
• Display filter literal strings can now be specified using raw
string syntax, identical to raw strings in the Python programming
language. This is useful to avoid the complexity of using two
levels of character escapes with regular expressions.
• 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 across all dialogs (Prepare Filter,
Analyse, RTP Player …)
• Follow stream is now able to follow SIP calls based on their
Call-ID value.
• Follow stream YAML output format’s has been changed to add
timestamps and peers information (for more details see the user’s
guide, Following Protocol Streams[3])
• IP fragments between public IPv4 addresses are now reassembled
even if they have different VLAN IDs. Reassembly of IP fragments
where one endpoint is a private (RFC 1918 section 3) or
link-local (RFC 3927) IPv4 address continues to take the VLAN ID
into account, as those addresses can be reused. To revert to the
previous behavior and not reassemble fragments with different
VLAN IDs, turn on the "Enable stricter conversation tracking
heuristics" top level protocol preference.
• USB Link Layer reassembly has been added, which allows hardware
captures to be analyzed at the same level as software captures.
• TShark can now export TLS session keys with the
--export-tls-session-keys option.
• Wireshark participated in the Google Season of Docs 2020 and the
User’s Guide has been extensively updated.
• Format of export to CSV in RTP Stream Analysis dialog was
slightly changed. First line of export contains names of columns
as in other CSV exports.
• Wireshark now supports the Turkish language.
• The settings in the 'Import from Hex Dump' dialog is now stored
in a profile import_hexdump.json file.
New File Format Decoding Support
Vector Informatik Binary Log File (BLF)
New Protocol Support
Bluetooth Link Manager Protocol (BT LMP), E2 Application Protocol
(E2AP), Event Tracing for Windows (ETW), High-Performance
Connectivity Tracer (HiPerConTracer), ISO 10681, Kerberos SPAKE,
Linux psample protocol, Local Interconnect Network (LIN), Microsoft
Task Scheduler Service, O-RAN E2AP, O-RAN fronthaul UC-plane (O-RAN),
Opus Interactive Audio Codec (OPUS), PDU Transport Protocol, R09.x
(R09), RDP Dynamic Channel Protocol (DRDYNVC), Real-Time
Publish-Subscribe Virtual Transport (RTPS-VT), Real-Time
Publish-Subscribe Wire Protocol (processed) (RTPS-PROC), Shared
Memory Communications (SMC), Signal PDU, SparkplugB, State
Synchronization Protocol (SSyncP), Tagged Image File Format (TIFF),
TP-Link Smart Home Protocol, UAVCAN DSDL, UAVCAN/CAN, Van Jacobson
PPP compression (VJC), and World of Warcraft World (WOWW)
Updated Protocol Support
Too many protocols have been updated to list here.
New and Updated Capture File Support
Vector Informatik Binary Log File (BLF)
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[4] 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[5] 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[6].
Bugs and feature requests can be reported on the issue tracker[7].
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site[8].
Last updated 2021-09-19 09:05:35 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/docs/wsug_html_chunked//ChAdvFollowStrea
mSection.html
4. https://www.wireshark.org/download.html#thirdparty
5. https://ask.wireshark.org/
6. https://www.wireshark.org/lists/
7. https://gitlab.com/wireshark/wireshark/-/issues
8. https://www.wireshark.org/faq.html
|
