forked from osmocom/wireshark
[Automatic update for 2022-08-21]
Update manuf, services enterprise numbers, translations, and other items.
This commit is contained in:
parent
ccf720d95d
commit
70dbe58aea
2
AUTHORS
2
AUTHORS
|
@ -4177,6 +4177,7 @@ Charles Nepveu <charles.nepveu[AT]verint.com>
|
|||
Charlie Lenahan <clenahan[AT]sonicbison.com>
|
||||
Chema Gonzalez <chemag[AT]fb.com>
|
||||
Chema Gonzalez <chemag[AT]gmail.com>
|
||||
Chien Wong <m[AT]xv97.com>
|
||||
Chloe Pelling <cpelling[AT]google.com>
|
||||
Chris Bontje <chris_bontje[AT]selinc.com>
|
||||
Chris Brandson <chris.brandson[AT]gmail.com>
|
||||
|
@ -4950,6 +4951,7 @@ Stella Randall <stella.randall[AT]emeerson.com>
|
|||
Stephan Kappertz <octopus.sk[AT]googlemail.com>
|
||||
Stephane Bryant <stephane.ml.bryant[AT]gmail.com>
|
||||
Stephen Donnelly <stephen.donnelly[AT]endace.com>
|
||||
Stephen Hemminger <stephen[AT]networkplumber.org>
|
||||
Steve Osselton <steve.osselton[AT]gmail.com>
|
||||
Stijn Last <stijn.last[AT]barco.com>
|
||||
Stéphane Lapie <stephane.lapie[AT]darkbsd.org>
|
||||
|
|
403
NEWS
403
NEWS
|
@ -1,7 +1,7 @@
|
|||
Wireshark 3.7.3 Release Notes
|
||||
Wireshark 4.1.0 Release Notes
|
||||
|
||||
This is an experimental release intended to test new features for
|
||||
Wireshark 4.0.
|
||||
Wireshark 4.2.
|
||||
|
||||
What is Wireshark?
|
||||
|
||||
|
@ -10,390 +10,22 @@ Wireshark 3.7.3 Release Notes
|
|||
|
||||
What’s New
|
||||
|
||||
Note: We do not ship official 32-bit Windows packages for this branch.
|
||||
If you need to use Wireshark on that platform, please install the
|
||||
latest 3.6 release. Issue 17779[1]
|
||||
|
||||
• The display filter syntax is now more powerful with many new
|
||||
extensions. See below for details.
|
||||
|
||||
• The Conversation and Endpoint dialogs have been redesigned with
|
||||
the following improvements:
|
||||
|
||||
• The context menu now includes the option to resize all columns,
|
||||
as well as copying elements.
|
||||
|
||||
• Data may be exported as JSON.
|
||||
|
||||
• Tabs may be detached and reattached from the dialog.
|
||||
|
||||
• Adding/Removing tabs will keep them in the same order all the
|
||||
time.
|
||||
|
||||
• If a filter is applied, two columns are shown in either dialog
|
||||
detailing the difference between unmatched and matched packets.
|
||||
|
||||
• Columns are now sorted via secondary properties if an identical
|
||||
entry is found.
|
||||
|
||||
• Conversations will be sorted via second address and first port
|
||||
number.
|
||||
|
||||
• Endpoints will be sorted via port numbers.
|
||||
|
||||
• IPv6 addresses are sorted correctly after IPv4 addresses.
|
||||
|
||||
• The dialog elements have been moved to make it easier to handle
|
||||
for new users.
|
||||
|
||||
• Selection of tap elements is done via list.
|
||||
|
||||
• All configurations and options are done via a left side button
|
||||
row.
|
||||
|
||||
• Columns for the Conversations and Endpoint dialogs can be
|
||||
hidden by context menu.
|
||||
|
||||
• TCP/UDP conversations now include the stream id and allows
|
||||
filtering on it.
|
||||
|
||||
• Speed when using MaxMind geolocation has been greatly improved.
|
||||
|
||||
• The Wireshark Lua API now uses the lrexlib[2] bindings to PCRE2.
|
||||
Code using the Lua GRegex module will have to be updated to use
|
||||
lrexlib-pcre2 instead. In most cases the API should be compatible
|
||||
and the conversion just requires a module name change.
|
||||
|
||||
• The tap registration system has been updated and the list of
|
||||
arguments for tap_packet_cb has changed. All taps registered
|
||||
through register_tap_listener have to be updated.
|
||||
|
||||
• The PCRE2 library[3] is now a required dependency to build
|
||||
Wireshark.
|
||||
|
||||
• You must now have a compiler with C11 support in order to build
|
||||
Wireshark.
|
||||
|
||||
• The following libraries and tools have had their minimum required
|
||||
version increased:
|
||||
|
||||
• CMake 3.10 is required on macOS and Linux.
|
||||
|
||||
• Qt version 5.12 (was 5.6.0), although compilation with 5.10 and
|
||||
5.11 is still possible, but will trigger a warning during
|
||||
configuration.
|
||||
|
||||
• Windows SDK 10.0.18362.0 is required due to issues with C11
|
||||
support.
|
||||
|
||||
• macOS version 10.10 (was 10.8) is required, if the Qt version
|
||||
is to be built, at least 10.11 is required, depending on the Qt
|
||||
version used (see below).
|
||||
|
||||
• GLib version 2.50.0 (was 2.38.0) is required.
|
||||
|
||||
• Libgcrypt version 1.8.0 (was 1.5.0) is required.
|
||||
|
||||
• c-ares version 1.14.0 (was 1.5.0).
|
||||
|
||||
• Python version 3.6.0 (was 3.4.0).
|
||||
|
||||
• GnuTLS version 3.5.8 (was 3.3.0).
|
||||
|
||||
• Nghttp2 minimum version has been set to 1.11.0 (none previous).
|
||||
|
||||
• For building with Qt on macOS, the following versions are required
|
||||
depending on the Qt version to be used:
|
||||
|
||||
• Qt 5.10 or higher requires macOS version 10.11
|
||||
|
||||
• Qt 5.12 or higher requires macOS version 10.12
|
||||
|
||||
• Qt 5.14 or higher requires macOS version 10.13
|
||||
|
||||
• Qt 6.0 or higher requires macOS version 10.14
|
||||
|
||||
• Perl is no longer required to build Wireshark, but may be required
|
||||
to build some source code files and run code analysis checks.
|
||||
|
||||
Many other 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.7.2:
|
||||
|
||||
The following features are new (or have been significantly updated)
|
||||
since version 3.7.1:
|
||||
|
||||
• The 'v' (lower case) and 'V' (upper case) switches have been
|
||||
swapped for editcap and mergecap to match the other command line
|
||||
utilities.
|
||||
|
||||
• The ip.flags field is now only the three high bits, not the full
|
||||
byte. Display filters and Coloring rules using the field will
|
||||
need to be adjusted.
|
||||
|
||||
• New address type AT_NUMERIC allows simple numeric addresses for
|
||||
protocols which do not have a more common-style address approach,
|
||||
analog to AT_STRINGZ.
|
||||
|
||||
The following features are new (or have been significantly updated)
|
||||
since version 3.7.0:
|
||||
|
||||
• The Windows installers now ship with Qt 6.2.3. They previously
|
||||
shipped with Qt 6.2.4.
|
||||
|
||||
• The Conversation and Endpoint dialogs have been reworked
|
||||
extensively
|
||||
|
||||
The following features are new (or have been significantly updated)
|
||||
since version 3.6.0:
|
||||
|
||||
• The Windows installers now ship with Npcap 1.60. They previously
|
||||
shipped with Npcap 1.55.
|
||||
|
||||
• The Windows installers now ship with Qt 6.2.4. They previously
|
||||
shipped with Qt 5.12.2.
|
||||
|
||||
• The display filter syntax has been updated and enhanced:
|
||||
|
||||
• A syntax to match a specific layer in the protocol stack has
|
||||
been added. For example in an IP-over-IP packet “ip.addr#1 ==
|
||||
1.1.1.1” matches the outer layer addresses and “ip.addr#2 ==
|
||||
1.1.1.2” matches the inner layer addresses.
|
||||
|
||||
• Universal quantifiers "any" and "all" have been added to any
|
||||
relational operator. For example the expression "all tcp.port ›
|
||||
1024" is true if and only if all tcp.port fields match the
|
||||
condition. Previously only the default behaviour to return true
|
||||
if any one field matches was supported.
|
||||
|
||||
• Field references, of the form ${some.field}, are now part of
|
||||
the syntax of display filters. Previously they were implemented
|
||||
as macros. The new implementation is more efficient and has the
|
||||
same properties as protocol fields, like matching on multiple
|
||||
values using quantifiers and support for layer filtering.
|
||||
|
||||
• Arithmetic is supported for numeric fields with the usual
|
||||
operators “+”, “-”, “*”, “/”, and “%”. Arithmetic expressions
|
||||
must be grouped using curly brackets (not parenthesis).
|
||||
|
||||
• New display filter functions max(), min() and abs() have been
|
||||
added.
|
||||
|
||||
• Functions can accept expressions as arguments, including other
|
||||
functions. Previously only protocol fields and slices were
|
||||
syntactically valid function arguments.
|
||||
|
||||
• A new syntax to disambiguate literals from identifiers has
|
||||
been added. Every value with a leading dot is a protocol or
|
||||
protocol field. Every value in between angle brackets is a
|
||||
literal value. See the User’s Guide[4] for details.
|
||||
|
||||
• The "bitwise and" operator is now a first-class bit operator,
|
||||
not a boolean operator. In particular this means it is now
|
||||
possible to mask bits, e.g.: frame[0] & 0x0F == 3.
|
||||
|
||||
• Dates and times can be given in UTC using ISO 8601 (with 'Z'
|
||||
timezone) or by appending the suffix "UTC" to the legacy formats.
|
||||
Otherwise local time is used.
|
||||
|
||||
• Integer literal constants may be written in binary (in
|
||||
addition to decimal/octal/hexadecimal) using the prefix "0b" or
|
||||
"0B".
|
||||
|
||||
• Logical AND now has higher precedence than logical OR, in line
|
||||
with most programming languages.
|
||||
|
||||
• It is now possible to index protocol fields from the end using
|
||||
negative indexes. For example the following expression tests the
|
||||
last two bytes of the TCP protocol field: tcp[-2:] == AA:BB. This
|
||||
was a longstanding bug that has been fixed in this release.
|
||||
|
||||
• Set elements must be separated using a comma, e.g: {1, 2,
|
||||
"foo"}. Using only whitespace as a separator was deprecated in
|
||||
3.6 and is now a syntax error.
|
||||
|
||||
• Support for some additional character escape sequences in
|
||||
double quoted strings has been added. Along with octal
|
||||
(\<number>) and hex (\x<number>) encoding, the following C escape
|
||||
sequences are now supported with the same meaning: \a, \b, \f,
|
||||
\n, \r, \t, \v. Previously they were only supported with
|
||||
character constants.
|
||||
|
||||
• Unicode universal character names are now supported with the
|
||||
escape sequences \uNNNN or \UNNNNNNNN, where N is a hexadecimal
|
||||
digit.
|
||||
|
||||
• Unrecognized escape sequences are now treated as a syntax
|
||||
error. Previously they were treated as a literal character. In
|
||||
addition to the sequences indicated above, backslash, single
|
||||
quotation and double quotation mark are also valid sequences: \\,
|
||||
\', \".
|
||||
|
||||
• A new strict equality operator "===" or "all_eq" has been
|
||||
added. The expression "a === b" is true if and only if all a’s
|
||||
are equal to b. The negation of "===" can now be written as "!=="
|
||||
(any_ne).
|
||||
|
||||
• The aliases "any_eq" for "==" and "all_ne" for "!=" have been
|
||||
added.
|
||||
|
||||
• The operator "~=" is deprecated and will be removed in a
|
||||
future version. Use "!==", which has the same meaning instead.
|
||||
|
||||
• Floats must be written with a leading and ending digit. For
|
||||
example the values ".7" and "7." are now invalid as floats. They
|
||||
must be written "0.7" and "7.0" respectively.
|
||||
|
||||
• The display filter engine now uses PCRE2 instead of GRegex
|
||||
(GLib’s bindings to the older and end-of-life PCRE library).
|
||||
PCRE2 is compatible with PCRE so any user-visible changes should
|
||||
be minimal. Some exotic patterns may now be invalid and require
|
||||
rewriting.
|
||||
|
||||
• Literal strings can handle embedded null bytes (the value
|
||||
'\0') correctly. This includes regular expression patterns. For
|
||||
example the double-quoted string "\0 is a null byte" is a legal
|
||||
literal value. This may be useful to match byte patterns but note
|
||||
that in general protocol fields with a string type still cannot
|
||||
contain embedded null bytes.
|
||||
|
||||
• Booleans can be written as True/TRUE or False/FALSE.
|
||||
Previously they could only be written as 1 or 0.
|
||||
|
||||
• It is now possible to test for the existence of a slice.
|
||||
|
||||
• All integer sizes are now compatible. Unless overflow occurs
|
||||
any integer field can be compared with any other.
|
||||
|
||||
• The `text2pcap` command and the “Import from Hex Dump” feature
|
||||
have been updated and enhanced:
|
||||
|
||||
• `text2pcap` supports writing the output file in all the
|
||||
capture file formats that wiretap library supports, using the
|
||||
same `-F` option as `editcap`, `mergecap`, and `tshark`.
|
||||
|
||||
• Consistent with the other command line tools like `editcap`,
|
||||
`mergecap`, `tshark`, and the "Import from Hex Dump" option
|
||||
within Wireshark, the default capture file format for `text2pcap`
|
||||
is now pcapng. The `-n` flag to select pcapng (instead of the
|
||||
previous default, pcap) has been deprecated and will be removed
|
||||
in a future release.
|
||||
|
||||
• `text2pcap` supports selecting the encapsulation type of the
|
||||
output file format using the wiretap library short names with an
|
||||
`-E` option, similar to the `-T` option of `editcap`.
|
||||
|
||||
• `text2pcap` has been updated to use the new logging output
|
||||
options and the `-d` flag has been removed. The "debug" log level
|
||||
corresponds to the old `-d` flag, and the "noisy" log level
|
||||
corresponds to using `-d` multiple times.
|
||||
|
||||
• `text2pcap` and “Import from Hex Dump” support writing fake
|
||||
IP, TCP, UDP, and SCTP headers to files with Raw IP, Raw IPv4,
|
||||
and Raw IPv6 encapsulations, in addition to Ethernet
|
||||
encapsulation available in previous versions.
|
||||
|
||||
• `text2pcap` supports scanning the input file using a custom
|
||||
regular expression, as supported in “Import from Hex Dump” in
|
||||
Wireshark 3.6.x.
|
||||
|
||||
• In general, `text2pcap` and wireshark’s “Import from Hex Dump”
|
||||
have feature parity.
|
||||
|
||||
• The default main window layout has been changed so that the
|
||||
Packet Detail and Packet Bytes are side by side underneath the
|
||||
Packet List pane.
|
||||
|
||||
• The HTTP2 dissector now supports using fake headers to parse the
|
||||
DATAs of streams captured without first HEADERS frames of a
|
||||
long-lived stream (such as a gRPC streaming call which allows
|
||||
sending many request or response messages in one HTTP2 stream).
|
||||
Users can specify fake headers using an existing stream’s server
|
||||
port, stream id and direction.
|
||||
|
||||
• The IEEE 802.11 dissector supports Mesh Connex (MCX).
|
||||
|
||||
• The “Capture Options” dialog contains the same configuration icon
|
||||
as the Welcome Screen. It is now possible to configure interfaces
|
||||
there.
|
||||
|
||||
• The “Extcap” dialog remembers password items during runtime,
|
||||
which makes it possible to run extcaps multiple times in row
|
||||
without having to reenter the password each time. Passwords are
|
||||
never stored on disk.
|
||||
|
||||
• It is possible to set extcap passwords in `tshark` and other CLI
|
||||
tools.
|
||||
|
||||
• The extcap configuration dialog now supports and remembers empty
|
||||
strings. There are new buttons to reset values back to their
|
||||
defaults.
|
||||
|
||||
• Support to display JSON mapping for Protobuf message has been
|
||||
added.
|
||||
|
||||
• macOS debugging symbols are now shipped in separate packages,
|
||||
similar to Windows packages.
|
||||
|
||||
• In the ZigBee ZCL Messaging dissector the
|
||||
zbee_zcl_se.msg.msg_ctrl.depreciated field has been renamed to
|
||||
zbee_zcl_se.msg.msg_ctrl.deprecated
|
||||
|
||||
• The interface list on the welcome page sorts active interfaces
|
||||
first and only displays sparklines for active interfaces.
|
||||
Additionally, the interfaces can now be hidden and shown via the
|
||||
context menu in the interface list
|
||||
|
||||
• The Event Tracing for Windows (ETW) file reader now supports
|
||||
displaying IP packets from an event trace logfile or an event
|
||||
trace live session.
|
||||
|
||||
• ciscodump now supports IOS, IOS-XE and ASA remote capturing
|
||||
|
||||
Removed Features and Support
|
||||
|
||||
• The CMake options starting with DISABLE_something were renamed
|
||||
ENABLE_something for consistency. For example DISABLE_WERROR=On
|
||||
became ENABLE_WERROR=Off. The default values are unchanged.
|
||||
since version 4.0.0:
|
||||
|
||||
New Protocol Support
|
||||
|
||||
Allied Telesis Loop Detection (AT LDF), AUTOSAR I-PDU Multiplexer
|
||||
(AUTOSAR I-PduM), DTN Bundle Protocol Security (BPSec), DTN Bundle
|
||||
Protocol Version 7 (BPv7), DTN TCP Convergence Layer Protocol
|
||||
(TCPCL), DVB Selection Information Table (DVB SIT), Enhanced Cash
|
||||
Trading Interface 10.0 (XTI), Enhanced Order Book Interface 10.0
|
||||
(EOBI), Enhanced Trading Interface 10.0 (ETI), FiveCo’s Legacy
|
||||
Register Access Protocol (5co-legacy), Generic Data Transfer Protocol
|
||||
(GDT), gRPC Web (gRPC-Web), Host IP Configuration Protocol (HICP),
|
||||
Locamation Interface Module (IDENT, CALIBRATION, SAMPLES - IM1,
|
||||
SAMPLES - IM2R0), Mesh Connex (MCX), Microsoft Cluster Remote Control
|
||||
Protocol (RCP), Protected Extensible Authentication Protocol (PEAP),
|
||||
Realtek, REdis Serialization Protocol v2 (RESP), Roon Discovery
|
||||
(RoonDisco), Secure File Transfer Protocol (sftp), Secure Host IP
|
||||
Configuration Protocol (SHICP), SSH File Transfer Protocol (SFTP),
|
||||
USB Attached SCSI (UASP), and ZBOSS NCP
|
||||
|
||||
Updated Protocol Support
|
||||
|
||||
Too many protocols have been updated to list here.
|
||||
|
||||
New and Updated Capture File Support
|
||||
|
||||
Major API Changes
|
||||
|
||||
• proto.h: The field display types "STR_ASCII" and "STR_UNICODE"
|
||||
have been removed. Use "BASE_NONE" instead.
|
||||
|
||||
• proto.h: The field display types for floats have been extended
|
||||
and refactored. The type BASE_FLOAT has been removed. Use
|
||||
BASE_NONE instead. New display types for floats are BASE_DEC,
|
||||
BASE_HEX, BASE_EXP and BASE_CUSTOM.
|
||||
|
||||
Getting Wireshark
|
||||
|
||||
Wireshark source code and installation packages are available from
|
||||
|
@ -404,7 +36,7 @@ Wireshark 3.7.3 Release Notes
|
|||
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[5] on the Wireshark web site.
|
||||
be found on the download page[1] on the Wireshark web site.
|
||||
|
||||
File Locations
|
||||
|
||||
|
@ -419,25 +51,24 @@ Wireshark 3.7.3 Release Notes
|
|||
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[6] and on the
|
||||
Community support is available on Wireshark’s Q&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[7].
|
||||
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[8].
|
||||
Bugs and feature requests can be reported on the issue tracker[4].
|
||||
|
||||
You can learn protocol analysis and meet Wireshark’s developers at
|
||||
SharkFest[5].
|
||||
|
||||
Frequently Asked Questions
|
||||
|
||||
A complete FAQ is available on the Wireshark web site[9].
|
||||
A complete FAQ is available on the Wireshark web site[6].
|
||||
|
||||
References
|
||||
|
||||
1. https://gitlab.com/wireshark/wireshark/-/issues/17779
|
||||
2. https://github.com/rrthomas/lrexlib
|
||||
3. https://www.pcre.org/
|
||||
4. https://www.wireshark.org/docs/wsug_html_chunked/ChWorkBuildDispla
|
||||
yFilterSection.html#_some_protocol_names_can_be_ambiguous
|
||||
5. https://www.wireshark.org/download.html
|
||||
6. https://ask.wireshark.org/
|
||||
7. https://www.wireshark.org/lists/
|
||||
8. https://gitlab.com/wireshark/wireshark/-/issues
|
||||
9. https://www.wireshark.org/faq.html
|
||||
1. https://www.wireshark.org/download.html
|
||||
2. https://ask.wireshark.org/
|
||||
3. https://www.wireshark.org/lists/
|
||||
4. https://gitlab.com/wireshark/wireshark/-/issues
|
||||
5. https://sharkfest.wireshark.org
|
||||
6. https://www.wireshark.org/faq.html
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Capinfos (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Capinfos (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Print various information (infos) about capture files.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Dumpcap (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Dumpcap (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Capture network packets and dump them into a pcapng or pcap file.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Editcap (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Editcap (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Edit and/or translate the format of capture files.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Mergecap (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Mergecap (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Merge two or more capture files into one.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Rawshark (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Rawshark (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Dump and analyze network traffic.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Reordercap (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Reordercap (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Reorder timestamps of input file frames into output file.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Text2pcap (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Text2pcap (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Generate a capture file from an ASCII hexdump of packets.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
TShark (Wireshark) 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
TShark (Wireshark) 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Dump and analyze network traffic.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Wireshark 3.7.3 (v3.7.3rc0-25-g72703582d587)
|
||||
Wireshark 4.1.0 (v4.1.0rc0-55-gccf720d95daf)
|
||||
Interactively dump and analyze network traffic.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
# The format used here is: <NUMERICAL_ID><SPACE><NAME>
|
||||
# Where SPACE can be any sequence of spaces and tabs.
|
||||
#
|
||||
# (last updated 2022-08-14)
|
||||
# (last updated 2022-08-21)
|
||||
|
||||
0 Reserved
|
||||
1 NxNetworks
|
||||
|
@ -44091,7 +44091,7 @@
|
|||
44269 Beamly
|
||||
44270 Barnardsoft Co., Ltd.
|
||||
44271 Nuage Networks
|
||||
44272 PRO-PflegeBeratung
|
||||
44272 Peter Andree
|
||||
44273 Gernert-Net
|
||||
44274 Trit Networks LLC
|
||||
44275 Illumio, Inc.
|
||||
|
@ -54409,7 +54409,7 @@
|
|||
54606 Scalstrm AB
|
||||
54607 Epsom & St Helier University Hospitals NHS Trust
|
||||
54608 Definium Technologies
|
||||
54609 Centurion Consulting et. Cie. GbR
|
||||
54609 Centurion Intelligence Consulting Agency
|
||||
54610 OOO "NTC Rotek"
|
||||
54611 Stichting Casade
|
||||
54612 Chicago Digital Power
|
||||
|
@ -59041,3 +59041,29 @@
|
|||
59249 iTik
|
||||
59250 Ankh-Morp.ORG
|
||||
59251 LeiSec GmbH
|
||||
59252 Rapidmax Technology Corporation
|
||||
59253 Shenzhen FinDreams Battery Co., Ltd.
|
||||
59254 bibliotheca AG
|
||||
59255 SPECIAL AGENT SERVICES DBA JET AFFILIATIONS
|
||||
59256 Alphaledger
|
||||
59257 RackN Inc.
|
||||
59258 RHS Research LLC
|
||||
59259 Progeek Consulting, LLC
|
||||
59260 Nanbu works Inc.
|
||||
59261 pme Familienservice GmbH
|
||||
59262 Retail Navigator LLC
|
||||
59263 Siemens DigitSphere
|
||||
59264 Bustec s.r.o.
|
||||
59265 Bayerische Staatsbrauerei Weihenstephan
|
||||
59266 TriNetX LLC
|
||||
59267 Window Nation LLC
|
||||
59268 Sol-Ark
|
||||
59269 iPoxo IT GmbH
|
||||
59270 Novella Satcoms ltd
|
||||
59271 Clearpoint Business Group, LLC.
|
||||
59272 Golden Rings Technologies Co., LTD
|
||||
59273 Shenzhen 3SNIC information technology company Limited
|
||||
59274 ReadyOp Communications, Inc.
|
||||
59275 MadfooatCom For Electronic Payments
|
||||
59276 EXATERRA LTD
|
||||
59277 SWN Stadtwerke Northeim GmbH
|
||||
|
|
Can't render this file because it is too large.
|
|
@ -1477,7 +1477,7 @@ const value_string tls_cert_status_type[] = {
|
|||
};
|
||||
|
||||
/* Generated by tools/make-tls-ct-logids.py
|
||||
* Last-Modified Tue, 02 Aug 2022 11:08:00 GMT, 114 entries. */
|
||||
* Last-Modified Sat, 20 Aug 2022 09:48:00 GMT, 117 entries. */
|
||||
static const bytes_string ct_logids[] = {
|
||||
{ (const guint8[]){
|
||||
0xfa, 0xd4, 0xc9, 0x7c, 0xc4, 0x9e, 0xe2, 0xf8, 0xac, 0x85, 0xc5,
|
||||
|
@ -1707,6 +1707,12 @@ static const bytes_string ct_logids[] = {
|
|||
0x3b, 0xd2, 0x2b, 0xc1, 0x3a, 0x57, 0xa3, 0x52, 0xeb, 0x52,
|
||||
},
|
||||
32, "Cloudflare 'Nimbus2023' Log" },
|
||||
{ (const guint8[]){
|
||||
0xda, 0xb6, 0xbf, 0x6b, 0x3f, 0xb5, 0xb6, 0x22, 0x9f, 0x9b, 0xc2,
|
||||
0xbb, 0x5c, 0x6b, 0xe8, 0x70, 0x91, 0x71, 0x6c, 0xbb, 0x51, 0x84,
|
||||
0x85, 0x34, 0xbd, 0xa4, 0x3d, 0x30, 0x48, 0xd7, 0xfb, 0xab,
|
||||
},
|
||||
32, "Cloudflare 'Nimbus2024' Log" },
|
||||
{ (const guint8[]){
|
||||
0x56, 0x14, 0x06, 0x9a, 0x2f, 0xd7, 0xc2, 0xec, 0xd3, 0xf5, 0xe1,
|
||||
0xbd, 0x44, 0xb2, 0x3e, 0xc7, 0x46, 0x76, 0xb9, 0xbc, 0x99, 0x11,
|
||||
|
@ -2019,6 +2025,18 @@ static const bytes_string ct_logids[] = {
|
|||
0x35, 0xc4, 0x9e, 0x1d, 0x09, 0x81, 0x25, 0xed, 0xb4, 0x99,
|
||||
},
|
||||
32, "Let's Encrypt 'Oak2023' log" },
|
||||
{ (const guint8[]){
|
||||
0x3b, 0x53, 0x77, 0x75, 0x3e, 0x2d, 0xb9, 0x80, 0x4e, 0x8b, 0x30,
|
||||
0x5b, 0x06, 0xfe, 0x40, 0x3b, 0x67, 0xd8, 0x4f, 0xc3, 0xf4, 0xc7,
|
||||
0xbd, 0x00, 0x0d, 0x2d, 0x72, 0x6f, 0xe1, 0xfa, 0xd4, 0x17,
|
||||
},
|
||||
32, "Let's Encrypt 'Oak2024H1' log" },
|
||||
{ (const guint8[]){
|
||||
0x3f, 0x17, 0x4b, 0x4f, 0xd7, 0x22, 0x47, 0x58, 0x94, 0x1d, 0x65,
|
||||
0x1c, 0x84, 0xbe, 0x0d, 0x12, 0xed, 0x90, 0x37, 0x7f, 0x1f, 0x85,
|
||||
0x6a, 0xeb, 0xc1, 0xbf, 0x28, 0x85, 0xec, 0xf8, 0x64, 0x6e,
|
||||
},
|
||||
32, "Let's Encrypt 'Oak2024H2' log" },
|
||||
{ (const guint8[]){
|
||||
0x23, 0x2d, 0x41, 0xa4, 0xcd, 0xac, 0x87, 0xce, 0xd9, 0xf9, 0x43,
|
||||
0xf4, 0x68, 0xc2, 0x82, 0x09, 0x5a, 0xe0, 0x9d, 0x30, 0xd6, 0x2e,
|
||||
|
|
|
@ -23685,6 +23685,7 @@ static const value_string usb_products_vals[] = {
|
|||
{ 0x25fb0179, "Pentax K1" },
|
||||
{ 0x25fb017b, "Pentax K3 II" },
|
||||
{ 0x25fb017d, "Pentax K70" },
|
||||
{ 0x25fb017f, "Pentax KP" },
|
||||
{ 0x25fb210b, "Ricoh WG-M2" },
|
||||
{ 0x26040012, "U12" },
|
||||
{ 0x2626ea60, "UART Bridge Controller [cp210x]" },
|
||||
|
|
103
manuf
103
manuf
|
@ -44,24 +44,24 @@
|
|||
# https://gitlab.com/wireshark/wireshark/-/raw/master/manuf
|
||||
|
||||
# http://standards-oui.ieee.org/cid/cid.csv:
|
||||
# Content-Length: 13056
|
||||
# Last-Modified: Sun, 14 Aug 2022 16:00:20 GMT
|
||||
# Content-Length: 13137
|
||||
# Last-Modified: Sun, 21 Aug 2022 16:00:38 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/iab/iab.csv:
|
||||
# Content-Length: 381461
|
||||
# Last-Modified: Sun, 14 Aug 2022 16:00:35 GMT
|
||||
# Last-Modified: Sun, 21 Aug 2022 16:00:54 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/oui/oui.csv:
|
||||
# Content-Length: 3010162
|
||||
# Last-Modified: Sun, 14 Aug 2022 16:01:14 GMT
|
||||
# Content-Length: 3016027
|
||||
# Last-Modified: Sun, 21 Aug 2022 16:01:34 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/oui28/mam.csv:
|
||||
# Content-Length: 480454
|
||||
# Last-Modified: Sun, 14 Aug 2022 16:00:44 GMT
|
||||
# Content-Length: 480682
|
||||
# Last-Modified: Sun, 21 Aug 2022 16:01:02 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/oui36/oui36.csv:
|
||||
# Content-Length: 453752
|
||||
# Last-Modified: Sun, 14 Aug 2022 16:01:04 GMT
|
||||
# Content-Length: 455065
|
||||
# Last-Modified: Sun, 21 Aug 2022 16:01:22 GMT
|
||||
|
||||
00:00:00 00:00:00 Officially Xerox, but 0:0:0:0:0:0 is more common
|
||||
00:00:01 Xerox Xerox Corporation
|
||||
|
@ -16723,6 +16723,7 @@
|
|||
00:C3:43 E-T-ACir E-T-A Circuit Breakers Ltd
|
||||
00:C3:F4 SamsungE Samsung Electronics Co.,Ltd
|
||||
00:C5:2C JuniperN Juniper Networks
|
||||
00:C5:85 Apple Apple, Inc.
|
||||
00:C5:DB Datatech Datatech Sistemas Digitales Avanzados SL
|
||||
00:C6:10 Apple Apple, Inc.
|
||||
00:C8:8B Cisco Cisco Systems, Inc
|
||||
|
@ -17367,6 +17368,7 @@
|
|||
02:E6:D3 NixdorfC Nixdorf Computer Corp.
|
||||
04:02:1F HuaweiTe Huawei Technologies Co.,Ltd
|
||||
04:02:CA Shenzhen Shenzhen Vtsonic Co.,ltd
|
||||
04:03:12 Hangzhou Hangzhou Hikvision Digital Technology Co.,Ltd.
|
||||
04:03:D6 Nintendo Nintendo Co.,Ltd
|
||||
04:04:B8 ChinaHua China Hualu Panasonic AVC Networks Co., LTD.
|
||||
04:04:EA ValensSe Valens Semiconductor Ltd.
|
||||
|
@ -17610,6 +17612,7 @@
|
|||
04:BA:8D SamsungE Samsung Electronics Co.,Ltd
|
||||
04:BA:D6 D-Link D-Link Corporation
|
||||
04:BB:F9 Pavilion Pavilion Data Systems Inc
|
||||
04:BC:6D Apple Apple, Inc.
|
||||
04:BC:87 Shenzhen Shenzhen JustLink Technology Co., LTD
|
||||
04:BC:9F Calix Calix Inc.
|
||||
04:BD:70 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
|
@ -18511,6 +18514,7 @@
|
|||
0C:AC:8A Sagemcom Sagemcom Broadband SAS
|
||||
0C:AE:7D TexasIns Texas Instruments
|
||||
0C:AE:BD EdifierI Edifier International
|
||||
0C:AF:31 Cisco Cisco Systems, Inc
|
||||
0C:AF:5A GenusPow Genus Power Infrastructures Limited
|
||||
0C:B0:88 AITeleco AITelecom
|
||||
0C:B2:B7 TexasIns Texas Instruments
|
||||
|
@ -18726,6 +18730,7 @@
|
|||
10:2D:31 Shenzhen Shenzhen Americas Trading Company LLC
|
||||
10:2D:41 SichuanA Sichuan AI-Link Technology Co., Ltd.
|
||||
10:2D:96 Looxcie Looxcie Inc.
|
||||
10:2E:00 IntelCor Intel Corporate
|
||||
10:2E:AF TexasIns Texas Instruments
|
||||
10:2F:6B Microsof Microsoft Corporation
|
||||
10:2F:A3 Shenzhen Shenzhen Uvision-tech Technology Co.Ltd
|
||||
|
@ -18880,6 +18885,7 @@
|
|||
10:9C:70 PrusaRes Prusa Research s.r.o.
|
||||
10:9D:7A HuaweiDe Huawei Device Co., Ltd.
|
||||
10:9E:3A Zhejiang Zhejiang Tmall Technology Co., Ltd.
|
||||
10:9F:4F NewH3CIn New H3C Intelligence Terminal Co., Ltd.
|
||||
10:9F:A9 Actionte Actiontec Electronics, Inc
|
||||
10:A1:3B Fujikura Fujikura Rubber Ltd.
|
||||
10:A2:4E Gold3Lin Gold3Link Electronics Co., Ltd
|
||||
|
@ -18912,6 +18918,7 @@
|
|||
10:B9:F7 Niko-Ser Niko-Servodan
|
||||
10:B9:FE Lika Lika srl
|
||||
10:BA:A5 GanaI&C Gana I&C Co., Ltd
|
||||
10:BB:F3 HunanFn- Hunan Fn-Link Technology Limited
|
||||
10:BC:97 vivoMobi vivo Mobile Communication Co., Ltd.
|
||||
10:BD:18 Cisco Cisco Systems, Inc
|
||||
10:BD:55 Q-Lab Q-Lab Corporation
|
||||
|
@ -19774,6 +19781,7 @@
|
|||
18:F8:7F WhaYuInd Wha Yu Industrial Co., Ltd.
|
||||
18:F9:C4 BAE BAE Systems
|
||||
18:FA:6F ISCappli ISC applied systems corp
|
||||
18:FA:B7 Apple Apple, Inc.
|
||||
18:FB:7B Dell Dell Inc.
|
||||
18:FC:26 QorvoInt Qorvo International Pte. Ltd.
|
||||
18:FC:9F ChangheE Changhe Electronics Co., Ltd.
|
||||
|
@ -19822,6 +19830,7 @@
|
|||
1C:17:D3 Cisco Cisco Systems, Inc
|
||||
1C:18:4A ShenZhen ShenZhen RicherLink Technologies Co.,LTD
|
||||
1C:19:DE eyevis eyevis GmbH
|
||||
1C:1A:1B Shanghai Shanghai Sunmi Technology Co.,Ltd.
|
||||
1C:1A:C0 Apple Apple, Inc.
|
||||
1C:1A:DF Microsof Microsoft Corporation
|
||||
1C:1B:0D Giga-Byt Giga-Byte Technology Co.,Ltd.
|
||||
|
@ -20017,6 +20026,7 @@
|
|||
1C:83:41 HefeiBit Hefei Bitland Information Technology Co.Ltd
|
||||
1C:83:B0 LinkedIP Linked IP GmbH
|
||||
1C:84:64 FormosaW Formosa Wireless Communication Corp.
|
||||
1C:86:82 Apple Apple, Inc.
|
||||
1C:86:9A SamsungE Samsung Electronics Co.,Ltd
|
||||
1C:86:AD Mct Mct Co., Ltd.
|
||||
1C:87:2C ASUSTekC ASUSTek COMPUTER INC.
|
||||
|
@ -20332,6 +20342,7 @@
|
|||
20:0B:16 TexasIns Texas Instruments
|
||||
20:0B:C7 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
20:0B:CF Nintendo Nintendo Co.,Ltd
|
||||
20:0C:86 GXIndia GX India Pvt Ltd
|
||||
20:0C:C8 Netgear
|
||||
20:0D:B0 Shenzhen Shenzhen Four Seas Global Link Network Technology Co., Ltd.
|
||||
20:0E:2B Apple Apple, Inc.
|
||||
|
@ -20349,6 +20360,7 @@
|
|||
20:17:42 LGElectr LG Electronics
|
||||
20:18:0E Shenzhen Shenzhen Sunchip Technology Co., Ltd
|
||||
20:1A:06 CompalIn Compal Information (Kunshan) Co., Ltd.
|
||||
20:1A:94 Apple Apple, Inc.
|
||||
20:1B:88 Dongguan Dongguan Liesheng Electronic Co., Ltd.
|
||||
20:1B:C9 JuniperN Juniper Networks
|
||||
20:1D:03 Elatec Elatec GmbH
|
||||
|
@ -20529,6 +20541,7 @@
|
|||
20:A6:0C XiaomiCo Xiaomi Communications Co Ltd
|
||||
20:A6:80 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
20:A6:CD HewlettP Hewlett Packard Enterprise
|
||||
20:A7:66 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
20:A7:83 miContro miControl GmbH
|
||||
20:A7:87 BointecT Bointec Taiwan Corporation Limited
|
||||
20:A7:F9 Shenzhen Shenzhen Olanboa Technology Co., Ltd
|
||||
|
@ -20997,6 +21010,7 @@
|
|||
28:06:1E NingboGl Ningbo Global Useful Electric Co.,Ltd
|
||||
28:06:8D Itl Itl, Llc
|
||||
28:07:0D Guangzho Guangzhou Winsound Information Technology Co.,Ltd.
|
||||
28:0A:EE RenesasE Renesas Electronics (Penang) Sdn. Bhd.
|
||||
28:0B:5C Apple Apple, Inc.
|
||||
28:0C:28 UnigenDa Unigen DataStorage Corporation
|
||||
28:0C:B8 Mikrosay Mikrosay Yazilim ve Elektronik A.S.
|
||||
|
@ -21187,6 +21201,7 @@
|
|||
28:8A:1C JuniperN Juniper Networks
|
||||
28:8C:B8 zte zte corporation
|
||||
28:8E:EC Apple Apple, Inc.
|
||||
28:8F:F6 Apple Apple, Inc.
|
||||
28:91:D0 StageTec Stage Tec Entwicklungsgesellschaft für professionelle Audiotechnik mbH
|
||||
28:92:4A HewlettP Hewlett Packard
|
||||
28:93:7D SichuanT Sichuan Tianyi Comheart Telecom Co.,LTD
|
||||
|
@ -21864,6 +21879,7 @@
|
|||
30:17:C8 Sony Sony Corporation
|
||||
30:18:CF DEOScont DEOS control systems GmbH
|
||||
30:19:66 SamsungE Samsung Electronics Co.,Ltd
|
||||
30:19:84 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
30:1A:28 MakoNetw Mako Networks Ltd
|
||||
30:1A:30 MakoNetw Mako Networks Ltd
|
||||
30:1A:BA Guangdon Guangdong Oppo Mobile Telecommunications Corp.,Ltd
|
||||
|
@ -22721,6 +22737,7 @@
|
|||
38:4F:F0 AzureWav AzureWave Technology Inc.
|
||||
38:52:1A Nokia
|
||||
38:52:47 HuaweiDe Huawei Device Co., Ltd.
|
||||
38:53:19 34EDDBAC 34ED LLC DBA Centegix
|
||||
38:53:9C Apple Apple, Inc.
|
||||
38:54:9B zte zte corporation
|
||||
38:56:10 CANDYHOU CANDY HOUSE, Inc.
|
||||
|
@ -23039,6 +23056,7 @@
|
|||
3C:04:61 ARRISGro ARRIS Group, Inc.
|
||||
3C:04:BF PRAVIS PRAVIS SYSTEMS Co.Ltd.,
|
||||
3C:05:18 SamsungE Samsung Electronics Co.,Ltd
|
||||
3C:05:8E HuaweiTe Huawei Technologies Co.,Ltd
|
||||
3C:05:AB ProductC Product Creation Studio
|
||||
3C:06:30 Apple Apple, Inc.
|
||||
3C:06:64 BeijingL Beijing Leagrid Technology Co.,Ltd.
|
||||
|
@ -23143,6 +23161,7 @@
|
|||
3C:39:E7:E0:00:00/28 Marposs Marposs Spa
|
||||
3C:39:E7:F0:00:00/28 Private
|
||||
3C:3A:73 Avaya Avaya Inc
|
||||
3C:3B:99 ItelMobi Itel Mobile Limited
|
||||
3C:3F:51 2Crsi
|
||||
3C:40:4F Guangdon Guangdong Pisen Electronics Co.,Ltd
|
||||
3C:41:0E Cisco Cisco Systems, Inc
|
||||
|
@ -24250,6 +24269,7 @@
|
|||
40:ED:98:C0:00:00/28 BloomSky BloomSky,Inc.
|
||||
40:ED:98:D0:00:00/28 Hangzhou Hangzhou GANX Technology Co.,Ltd.
|
||||
40:ED:98:E0:00:00/28 BordaTec Borda Technology
|
||||
40:ED:CF Apple Apple, Inc.
|
||||
40:EE:15 ZioncomE Zioncom Electronics (Shenzhen) Ltd.
|
||||
40:EE:DD HuaweiTe Huawei Technologies Co.,Ltd
|
||||
40:EF:4C Fihonest Fihonest communication co.,Ltd
|
||||
|
@ -24319,7 +24339,7 @@
|
|||
44:05:E8 twareLAB
|
||||
44:07:0B Google Google, Inc.
|
||||
44:09:B8 SalcompS Salcomp (Shenzhen) CO., LTD.
|
||||
44:0C:EE RobertBo Robert Bosch Elektronika Kft
|
||||
44:0C:EE RobertBo Robert Bosch Elektronikai Kft.
|
||||
44:0C:FD NetMan NetMan Co., Ltd.
|
||||
44:10:FE HuizhouF Huizhou Foryou General Electronics Co., Ltd.
|
||||
44:11:02 EDMIEuro EDMI Europe Ltd
|
||||
|
@ -24860,6 +24880,7 @@
|
|||
48:8D:36 Arcadyan Arcadyan Corporation
|
||||
48:8E:42 DIGALOG DIGALOG GmbH
|
||||
48:8E:EF HuaweiTe Huawei Technologies Co.,Ltd
|
||||
48:8F:4C shenzhen shenzhen trolink Technology Co.,Ltd
|
||||
48:8F:5A Routerbo Routerboard.com
|
||||
48:90:2F LGElectr LG Electronics (Mobile Communications)
|
||||
48:91:53 Weinmann Weinmann Geräte für Medizin GmbH + Co. KG
|
||||
|
@ -24993,6 +25014,7 @@
|
|||
4A:15:40 sasdelaH sas de la Halle aux Fours
|
||||
4A:19:1B ZigBeeAl ZigBee Alliance
|
||||
4A:5A:6F AppliedM Applied Materials
|
||||
4A:5A:A9 GoCodeIT GoCodeIT Inc
|
||||
4A:67:04 Reliable Reliable Robotics Corporation
|
||||
4A:72:06 CAIRE CAIRE, Inc.
|
||||
4A:7F:74 INTEC INTEC Inc.
|
||||
|
@ -25175,7 +25197,10 @@
|
|||
4C:74:A7:40:00:00/28 WuxiMicr Wuxi Micro Innovation Integrated Circuit Design Co., Ltd
|
||||
4C:74:A7:50:00:00/28 AgilityR Agility Robotics, Inc.
|
||||
4C:74:A7:60:00:00/28 ABBLVIns ABB LV Installation Materials Co., Ltd. Beijing
|
||||
4C:74:A7:70:00:00/28 CoreipTe Coreip Technology Private Limited
|
||||
4C:74:A7:90:00:00/28 SuzhouXi Suzhou XiongLi Technology Inc.
|
||||
4C:74:A7:A0:00:00/28 Raonark
|
||||
4C:74:A7:B0:00:00/28 traplink traplinked Gmbh
|
||||
4C:74:A7:C0:00:00/28 N3com
|
||||
4C:74:A7:D0:00:00/28 ddcpersi ddcpersia
|
||||
4C:74:BF Apple Apple, Inc.
|
||||
|
@ -25441,6 +25466,7 @@
|
|||
50:14:08 AiNET
|
||||
50:14:79 iRobot iRobot Corporation
|
||||
50:14:B5 RichfitI Richfit Information Technology Co., Ltd
|
||||
50:14:C1 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
50:17:FF Cisco Cisco Systems, Inc
|
||||
50:18:4C Platina Platina Systems Inc.
|
||||
50:1A:A5 GNNetcom GN Netcom A/S
|
||||
|
@ -25457,6 +25483,7 @@
|
|||
50:23:A2 Apple Apple, Inc.
|
||||
50:25:2B NethraIm Nethra Imaging Incorporated
|
||||
50:26:90 Fujitsu Fujitsu Limited
|
||||
50:27:A9 eero eero inc.
|
||||
50:27:C7 TECHNART TECHNART Co.,Ltd
|
||||
50:28:4A IntelCor Intel Corporate
|
||||
50:28:73 HuaweiDe Huawei Device Co., Ltd.
|
||||
|
@ -25511,6 +25538,7 @@
|
|||
50:46:AE Mercury Mercury Corporation
|
||||
50:48:77 HonorDev Honor Device Co., Ltd.
|
||||
50:48:EB BeijingH Beijing Haihejinsheng Network Technology Co. Ltd.
|
||||
50:49:21 Cisco Cisco Systems, Inc
|
||||
50:49:B0 SamsungE Samsung Electronics Co.,Ltd
|
||||
50:4A:5E Masimo Masimo Corporation
|
||||
50:4A:6E Netgear
|
||||
|
@ -26386,6 +26414,7 @@
|
|||
58:B6:23 BeijingX Beijing Xiaomi Mobile Software Co., Ltd
|
||||
58:B6:33 RuckusWi Ruckus Wireless
|
||||
58:B9:61 SOLEMEle SOLEM Electronique
|
||||
58:B9:65 Apple Apple, Inc.
|
||||
58:B9:E1 Crystalf Crystalfontz America, Inc.
|
||||
58:BA:D4 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
58:BC:27 Cisco Cisco Systems, Inc
|
||||
|
@ -27053,6 +27082,7 @@
|
|||
60:9F:9D CloudSwi CloudSwitch
|
||||
60:A1:0A SamsungE Samsung Electronics Co.,Ltd
|
||||
60:A1:1E WuhanMax Wuhan Maxsine Electric Co.,Ltd.
|
||||
60:A2:C6 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
60:A3:7D Apple Apple, Inc.
|
||||
60:A4:23 SiliconL Silicon Laboratories
|
||||
60:A4:4C ASUSTekC ASUSTek COMPUTER INC.
|
||||
|
@ -28087,7 +28117,7 @@
|
|||
6C:8D:C1 Apple Apple, Inc.
|
||||
6C:8F:B5 Microsof Microsoft Mobile Oy
|
||||
6C:90:B1 SanLogic SanLogic Inc
|
||||
6C:91:06 Private
|
||||
6C:91:06 KatenaCo Katena Computing Technologies
|
||||
6C:92:BF InspurEl Inspur Electronic Information Industry Co.,Ltd.
|
||||
6C:93:08 IEEERegi IEEE Registration Authority
|
||||
6C:93:08:00:00:00/28 Braums
|
||||
|
@ -28299,6 +28329,7 @@
|
|||
70:1F:3C SamsungE Samsung Electronics Co.,Ltd
|
||||
70:1F:53 Cisco Cisco Systems, Inc
|
||||
70:20:84 HonHaiPr Hon Hai Precision Industry Co., Ltd.
|
||||
70:22:FE Apple Apple, Inc.
|
||||
70:23:93 fos4X fos4X GmbH
|
||||
70:25:26 Nokia
|
||||
70:25:59 CyberTAN CyberTAN Technology Inc.
|
||||
|
@ -28538,6 +28569,7 @@
|
|||
70:AC:08 SiliconL Silicon Laboratories
|
||||
70:AC:D7 Shenzhen Shenzhen YOUHUA Technology Co., Ltd
|
||||
70:AD:54 MalvernI Malvern Instruments Ltd
|
||||
70:AE:D5 Apple Apple, Inc.
|
||||
70:AF:24 TPVision TP Vision Belgium NV
|
||||
70:AF:25 Nishiyam Nishiyama Industry Co.,LTD.
|
||||
70:AF:6A Shenzhen Shenzhen Fenglian Technology Co., Ltd.
|
||||
|
@ -29327,7 +29359,7 @@
|
|||
70:B3:D5:30:B0:00/36 AshTechn Ash Technologies
|
||||
70:B3:D5:30:C0:00/36 Sicon Sicon srl
|
||||
70:B3:D5:30:D0:00/36 Fiberbas Fiberbase
|
||||
70:B3:D5:30:E0:00/36 Private
|
||||
70:B3:D5:30:E0:00/36 Ecolonum Ecolonum Inc.
|
||||
70:B3:D5:30:F0:00/36 Cardinal Cardinal Scales Manufacturing Co
|
||||
70:B3:D5:31:00:00/36 ConservS Conserv Solutions
|
||||
70:B3:D5:31:10:00/36 GüntherS Günther Spelsberg GmbH + Co. KG
|
||||
|
@ -29813,7 +29845,7 @@
|
|||
70:B3:D5:4F:50:00/36 OrlacoPr Orlaco Products B.V.
|
||||
70:B3:D5:4F:60:00/36 DorletSa Dorlet Sau
|
||||
70:B3:D5:4F:70:00/36 Foxtel Foxtel srl
|
||||
70:B3:D5:4F:80:00/36 Private
|
||||
70:B3:D5:4F:80:00/36 Sicpa-Gs Sicpa Sa - Gss
|
||||
70:B3:D5:4F:90:00/36 OptoPrec OptoPrecision GmbH
|
||||
70:B3:D5:4F:A0:00/36 Thruvisi Thruvision Limited
|
||||
70:B3:D5:4F:B0:00/36 MASElett MAS Elettronica sas di Mascetti Sandro e C.
|
||||
|
@ -32810,6 +32842,7 @@
|
|||
74:2E:FC DirectPa DirectPacket Research, Inc,
|
||||
74:2F:68 AzureWav AzureWave Technology Inc.
|
||||
74:31:70 Arcadyan Arcadyan Technology Corporation
|
||||
74:31:74 Apple Apple, Inc.
|
||||
74:32:56 NT-wareS NT-ware Systemprg GmbH
|
||||
74:32:C2 Kyolis
|
||||
74:33:A6 Shenzhen Shenzhen SuperElectron Technology Co.,Ltd.
|
||||
|
@ -32845,6 +32878,7 @@
|
|||
74:4B:E9 Explorer Explorer Hypertech Co.,Ltd
|
||||
74:4C:A1 LiteonTe Liteon Technology Corporation
|
||||
74:4D:28 Routerbo Routerboard.com
|
||||
74:4D:6D HuaweiTe Huawei Technologies Co.,Ltd
|
||||
74:4D:79 Arrive Arrive Systems Inc.
|
||||
74:50:4E NewH3CTe New H3C Technologies Co., Ltd
|
||||
74:51:BA XiaomiCo Xiaomi Communications Co Ltd
|
||||
|
@ -33653,6 +33687,7 @@
|
|||
7C:26:34 ARRISGro ARRIS Group, Inc.
|
||||
7C:26:64 Sagemcom Sagemcom Broadband SAS
|
||||
7C:27:BC HuiZhouG Hui Zhou Gaoshengda Technology Co.,LTD
|
||||
7C:29:6F Apple Apple, Inc.
|
||||
7C:2A:31 IntelCor Intel Corporate
|
||||
7C:2A:CA Apple Apple, Inc.
|
||||
7C:2A:DB XiaomiCo Xiaomi Communications Co Ltd
|
||||
|
@ -34105,6 +34140,7 @@
|
|||
80:37:73 Netgear
|
||||
80:38:96 SHARP SHARP Corporation
|
||||
80:38:BC HuaweiTe Huawei Technologies Co.,Ltd
|
||||
80:38:D4 Fibercen Fibercentury Network Technology Co.,Ltd.
|
||||
80:38:FB IntelCor Intel Corporate
|
||||
80:38:FD LeapFrog LeapFrog Enterprises, Inc.
|
||||
80:39:8C SamsungE Samsung Electronics Co.,Ltd
|
||||
|
@ -34140,6 +34176,7 @@
|
|||
80:54:6A Shenzhen Shenzhen Gongjin Electronics Co.,Lt
|
||||
80:54:9C SamsungE Samsung Electronics Co.,Ltd
|
||||
80:54:D9 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
80:54:E3 Apple Apple, Inc.
|
||||
80:56:3C Zf
|
||||
80:56:F2 HonHaiPr Hon Hai Precision Ind. Co.,Ltd.
|
||||
80:57:19 SamsungE Samsung Electronics Co.,Ltd
|
||||
|
@ -34324,6 +34361,7 @@
|
|||
80:DA:C2 Technico Technicolor CH USA Inc.
|
||||
80:DB:17 JuniperN Juniper Networks
|
||||
80:DB:31 PowerQuo Power Quotient International Co., Ltd.
|
||||
80:DE:CC HYBE HYBE Co.,LTD
|
||||
80:E0:1D Cisco Cisco Systems, Inc
|
||||
80:E1:BF HuaweiTe Huawei Technologies Co.,Ltd
|
||||
80:E4:55 NewH3CTe New H3C Technologies Co., Ltd
|
||||
|
@ -34503,7 +34541,7 @@
|
|||
84:5C:F3 IntelCor Intel Corporate
|
||||
84:5D:D7 Shenzhen Shenzhen Netcom Electronics Co.,Ltd
|
||||
84:5F:04 SamsungE Samsung Electronics Co.,Ltd
|
||||
84:60:82 Private
|
||||
84:60:82 Hyperloo Hyperloop Technologies, Inc dba Virgin Hyperloop
|
||||
84:61:A0 ARRISGro ARRIS Group, Inc.
|
||||
84:62:23 Shenzhen Shenzhen Coship Electronics Co., Ltd.
|
||||
84:62:A6 EuroCBPh EuroCB (Phils), Inc.
|
||||
|
@ -34776,6 +34814,7 @@
|
|||
88:1B:99 Shenzhen Shenzhen Xin Fei Jia Electronic Co. Ltd.
|
||||
88:1C:95 ItelMobi Itel Mobile Limited
|
||||
88:1D:FC Cisco Cisco Systems, Inc
|
||||
88:1E:5A Apple Apple, Inc.
|
||||
88:1F:A1 Apple Apple, Inc.
|
||||
88:20:0D Apple Apple, Inc.
|
||||
88:20:12 LMITechn LMI Technologies
|
||||
|
@ -34790,6 +34829,7 @@
|
|||
88:25:93 Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
88:28:7D AltoBeam AltoBeam (China) Inc.
|
||||
88:28:B3 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
88:28:FB JuniperN Juniper Networks
|
||||
88:29:49 RenesasE Renesas Electronics (Penang) Sdn. Bhd.
|
||||
88:29:50 NetmoonT Netmoon Technology Co., Ltd
|
||||
88:29:9C SamsungE Samsung Electronics Co.,Ltd
|
||||
|
@ -35026,6 +35066,7 @@
|
|||
88:B6:6B easynetw easynetworks
|
||||
88:B6:EE DishTech Dish Technologies Corp
|
||||
88:B8:63 HisenseV Hisense Visual Technology Co.,Ltd
|
||||
88:B8:6F Infinixm Infinix mobility limited
|
||||
88:B8:D0 Dongguan Dongguan Koppo Electronic Co.,Ltd
|
||||
88:B9:45 Apple Apple, Inc.
|
||||
88:BA:7F Qfiednet Qfiednet Co., Ltd.
|
||||
|
@ -35220,6 +35261,7 @@
|
|||
8C:1F:64 IEEERegi IEEE Registration Authority
|
||||
8C:1F:64:00:00:00/36 SuzhouXi Suzhou Xingxiangyi Precision Manufacturing Co.,Ltd.
|
||||
8C:1F:64:00:30:00/36 Brighten Brighten Controls LLP
|
||||
8C:1F:64:00:90:00/36 Convergi Converging Systems Inc.
|
||||
8C:1F:64:00:C0:00/36 GuanShow Guan Show Technologe Co., Ltd.
|
||||
8C:1F:64:01:70:00/36 Farmote Farmote Limited
|
||||
8C:1F:64:01:A0:00/36 Paragraf
|
||||
|
@ -35252,10 +35294,12 @@
|
|||
8C:1F:64:0B:E0:00/36 Bnb
|
||||
8C:1F:64:0C:00:00/36 ActiveRe Active Research Limited
|
||||
8C:1F:64:0C:50:00/36 TechnipF TechnipFMC
|
||||
8C:1F:64:0D:50:00/36 RealD RealD, Inc.
|
||||
8C:1F:64:0D:60:00/36 AvdInnov Avd Innovation Limited
|
||||
8C:1F:64:0E:00:00/36 Autophar Autopharma
|
||||
8C:1F:64:0E:60:00/36 Cleanwat Cleanwatts Digital, S.A.
|
||||
8C:1F:64:0E:A0:00/36 SmartSky SmartSky Networks LLC
|
||||
8C:1F:64:0E:E0:00/36 RichSour Rich Source Precision IND., Co., LTD.
|
||||
8C:1F:64:0E:F0:00/36 Dave Dave Srl
|
||||
8C:1F:64:0F:00:00/36 Xylon
|
||||
8C:1F:64:0F:90:00/36 ikanInte ikan International LLC
|
||||
|
@ -35263,6 +35307,7 @@
|
|||
8C:1F:64:10:30:00/36 Kronotec Kronotech Srl
|
||||
8C:1F:64:11:10:00/36 Isac Isac Srl
|
||||
8C:1F:64:11:50:00/36 Neuralog Neuralog LP
|
||||
8C:1F:64:11:70:00/36 Grossenb Grossenbacher Systeme AG
|
||||
8C:1F:64:11:80:00/36 Automata Automata GmbH & Co. KG
|
||||
8C:1F:64:11:F0:00/36 NodeUDes NodeUDesign
|
||||
8C:1F:64:12:80:00/36 YulistaI Yulista Integrated Solution
|
||||
|
@ -35368,6 +35413,7 @@
|
|||
8C:1F:64:39:10:00/36 CpcUk Cpc (Uk)
|
||||
8C:1F:64:39:70:00/36 IntelCor Intel Corporate
|
||||
8C:1F:64:39:80:00/36 Software Software Systems Plus
|
||||
8C:1F:64:39:A0:00/36 GoldingA Golding Audio Ltd
|
||||
8C:1F:64:3A:40:00/36 QLMTechn QLM Technology Ltd
|
||||
8C:1F:64:3A:C0:00/36 BenisonT Benison Tech
|
||||
8C:1F:64:3A:D0:00/36 TowerIQ
|
||||
|
@ -35398,6 +35444,7 @@
|
|||
8C:1F:64:43:80:00/36 Integerp Integer.pl S.A.
|
||||
8C:1F:64:44:50:00/36 FigmentD Figment Design Laboratories
|
||||
8C:1F:64:44:E0:00/36 GVALight GVA Lighting, Inc.
|
||||
8C:1F:64:44:F0:00/36 RealD RealD, Inc.
|
||||
8C:1F:64:45:40:00/36 KJKlimat KJ Klimateknik A/S
|
||||
8C:1F:64:45:B0:00/36 BeijingA Beijing Aoxing Technology Co.,Ltd
|
||||
8C:1F:64:45:D0:00/36 FuzhouTu Fuzhou Tucsen Photonics Co.,Ltd
|
||||
|
@ -35640,6 +35687,7 @@
|
|||
8C:1F:64:91:10:00/36 Eolane
|
||||
8C:1F:64:91:80:00/36 AbbottDi Abbott Diagnostics Technologies AS
|
||||
8C:1F:64:91:A0:00/36 Profcon Profcon AB
|
||||
8C:1F:64:91:D0:00/36 enlighte enlighten
|
||||
8C:1F:64:92:30:00/36 MBconnec MB connect line GmbH Fernwartungssysteme
|
||||
8C:1F:64:92:A0:00/36 ThermoOn Thermo Onix Ltd
|
||||
8C:1F:64:92:D0:00/36 IVORInte IVOR Intelligent Electrical Appliance Co., Ltd
|
||||
|
@ -35697,6 +35745,7 @@
|
|||
8C:1F:64:A5:70:00/36 EkspertS EkspertStroyProekt
|
||||
8C:1F:64:A5:C0:00/36 Prosys
|
||||
8C:1F:64:A5:D0:00/36 Shenzhen Shenzhen zhushida Technology lnformation Co.,Ltd
|
||||
8C:1F:64:A6:00:00/36 ActiveOp Active Optical Systems, LLC
|
||||
8C:1F:64:A6:A0:00/36 SphereCo Sphere Com Services Pvt Ltd
|
||||
8C:1F:64:A6:D0:00/36 CyberneX CyberneX Co., Ltd
|
||||
8C:1F:64:A7:60:00/36 DEUTA-WE DEUTA-WERKE GmbH
|
||||
|
@ -35734,6 +35783,7 @@
|
|||
8C:1F:64:B5:50:00/36 SancharT Sanchar Telesystems limited
|
||||
8C:1F:64:B5:60:00/36 Arcvideo
|
||||
8C:1F:64:B6:40:00/36 GSPSprac GSP Sprachtechnologie GmbH
|
||||
8C:1F:64:B6:70:00/36 M2Mcraft M2M craft Co., Ltd.
|
||||
8C:1F:64:B7:30:00/36 Comm-enc Comm-ence, Inc.
|
||||
8C:1F:64:B7:70:00/36 Carestre Carestream Dental LLC
|
||||
8C:1F:64:B7:B0:00/36 Gateview Gateview Technologies
|
||||
|
@ -35890,9 +35940,11 @@
|
|||
8C:1F:64:EF:B0:00/36 Warecube Warecube,Inc
|
||||
8C:1F:64:F0:40:00/36 IoTSecur IoTSecure, LLC
|
||||
8C:1F:64:F1:20:00/36 CAITRON CAITRON GmbH
|
||||
8C:1F:64:F2:20:00/36 VoyageAu Voyage Audio LLC
|
||||
8C:1F:64:F2:50:00/36 MisakaNe Misaka Network, Inc.
|
||||
8C:1F:64:F2:70:00/36 Tesat-Sp Tesat-Spacecom GmbH & Co. KG
|
||||
8C:1F:64:F2:C0:00/36 Tunstall Tunstall A/S
|
||||
8C:1F:64:F2:D0:00/36 HUERNERS HUERNER Schweisstechnik GmbH
|
||||
8C:1F:64:F3:10:00/36 Internat International Water Treatment Maritime AS
|
||||
8C:1F:64:F3:20:00/36 Shenzhen Shenzhen INVT Electric Co.,Ltd
|
||||
8C:1F:64:F3:90:00/36 WeinanWi Weinan Wins Future Technology Co.,Ltd
|
||||
|
@ -35905,6 +35957,7 @@
|
|||
8C:1F:64:F4:50:00/36 Jbf
|
||||
8C:1F:64:F4:E0:00/36 ADAMCZEW ADAMCZEWSKI elektronische Messtechnik GmbH
|
||||
8C:1F:64:F5:20:00/36 AMFMedic AMF Medical SA
|
||||
8C:1F:64:F5:60:00/36 KC5Inter KC5 International Sdn Bhd
|
||||
8C:1F:64:F5:90:00/36 Inovonic Inovonics Inc.
|
||||
8C:1F:64:F5:A0:00/36 TelcoAnt Telco Antennas Pty Ltd
|
||||
8C:1F:64:F5:B0:00/36 SemaConn SemaConnect, Inc
|
||||
|
@ -36146,6 +36199,7 @@
|
|||
8C:96:5F Shandong Shandong Zhongan Technology Co., Ltd.
|
||||
8C:97:EA FreeboxS Freebox Sas
|
||||
8C:98:06 Shenzhen Shenzhen Sei Robotics Co.,Ltd
|
||||
8C:98:6B Apple Apple, Inc.
|
||||
8C:99:E6 TCTmobil TCT mobile ltd
|
||||
8C:9F:3B QingdaoH Qingdao Hisense Communications Co.,Ltd.
|
||||
8C:A0:48 BeijingN Beijing NeTopChip Technology Co.,LTD
|
||||
|
@ -38214,6 +38268,7 @@ A0:E9:DB NingboFr Ningbo FreeWings Technologies Co.,Ltd
|
|||
A0:EB:76 AirCUVE AirCUVE Inc.
|
||||
A0:EC:80 zte zte corporation
|
||||
A0:EC:F9 Cisco Cisco Systems, Inc
|
||||
A0:ED:6D UbeeInte Ubee Interactive Co., Limited
|
||||
A0:ED:CD Apple Apple, Inc.
|
||||
A0:ED:FB QuectelW Quectel Wireless Solutions Co.,Ltd.
|
||||
A0:EF:84 SeineIma Seine Image Int'l Co., Ltd
|
||||
|
@ -38276,6 +38331,7 @@ A4:11:63:C0:00:00/28 Viloc
|
|||
A4:11:63:D0:00:00/28 Shenzhen Shenzhen Zhishi Technology Co., Ltd.
|
||||
A4:11:63:E0:00:00/28 tinylogi tinylogics
|
||||
A4:11:94 Lenovo
|
||||
A4:11:BB Cisco Cisco Systems, Inc
|
||||
A4:12:32 Guangdon Guangdong Oppo Mobile Telecommunications Corp.,Ltd
|
||||
A4:12:42 NECPlatf NEC Platforms, Ltd.
|
||||
A4:13:4E Luxul
|
||||
|
@ -38832,6 +38888,7 @@ A8:77:E5 Shenzhen Shenzhen Chuangwei-Rgb Electronics Co.,Ltd
|
|||
A8:79:8D SamsungE Samsung Electronics Co.,Ltd
|
||||
A8:7B:39 Nokia Nokia Corporation
|
||||
A8:7C:01 SamsungE Samsung Electronics Co.,Ltd
|
||||
A8:7C:F8 Apple Apple, Inc.
|
||||
A8:7D:12 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
A8:7E:33 NokiaDan Nokia Danmark A/S
|
||||
A8:7E:EA IntelCor Intel Corporate
|
||||
|
@ -39075,6 +39132,7 @@ AC:3C:8E Flextron Flextronics Computing(Suzhou)Co.,Ltd.
|
|||
AC:3C:B4 Nilan Nilan A/S
|
||||
AC:3D:05 Instores Instorescreen Aisa
|
||||
AC:3D:75 Hangzhou Hangzhou Zhiway Technologies Co.,Ltd.
|
||||
AC:3E:B1 Google Google, Inc.
|
||||
AC:3F:A4 TaiyoYud Taiyo Yuden Co.,Ltd
|
||||
AC:40:EA C&TSolut C&T Solution Inc.
|
||||
AC:41:22 EclipseE Eclipse Electronic Systems Inc.
|
||||
|
@ -39271,6 +39329,7 @@ AC:C5:95 Graphite Graphite Systems
|
|||
AC:C6:62 MitraSta MitraStar Technology Corp.
|
||||
AC:C6:98 KohzuPre Kohzu Precision Co., Ltd.
|
||||
AC:C7:3F Vitsmo Vitsmo Co., Ltd.
|
||||
AC:C9:06 Apple Apple, Inc.
|
||||
AC:C9:35 Ness Ness Corporation
|
||||
AC:CA:54 TelldusT Telldus Technologies AB
|
||||
AC:CA:8E ODATechn ODA Technologies
|
||||
|
@ -39652,6 +39711,7 @@ B0:E4:5C SamsungE Samsung Electronics Co.,Ltd
|
|||
B0:E4:D5 Google Google, Inc.
|
||||
B0:E5:0E Nrg Nrg Systems Inc
|
||||
B0:E5:ED HuaweiTe Huawei Technologies Co.,Ltd
|
||||
B0:E5:EF Apple Apple, Inc.
|
||||
B0:E5:F9 Apple Apple, Inc.
|
||||
B0:E7:1D Shanghai Shanghai Maigantech Co.,Ltd
|
||||
B0:E7:54 2Wire 2Wire Inc
|
||||
|
@ -39850,6 +39910,7 @@ B4:6B:FC IntelCor Intel Corporate
|
|||
B4:6C:47 Panasoni Panasonic Appliances Company
|
||||
B4:6D:35 DalianSe Dalian Seasky Automation Co;Ltd
|
||||
B4:6D:83 IntelCor Intel Corporate
|
||||
B4:6D:C2 Shenzhen Shenzhen Bilian Electronic Co.,Ltd
|
||||
B4:6E:08 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
B4:6F:2D WahooFit Wahoo Fitness
|
||||
B4:70:64 SamsungE Samsung Electronics Co.,Ltd
|
||||
|
@ -40290,6 +40351,7 @@ B8:CD:93 Penetek Penetek, Inc
|
|||
B8:CD:A7 MaxelerT Maxeler Technologies Ltd.
|
||||
B8:CE:F6 Mellanox Mellanox Technologies, Inc.
|
||||
B8:D0:6F Guangzho Guangzhou Hkust Fok Ying Tung Research Institute
|
||||
B8:D0:F0 FcntLmit Fcnt Lmited
|
||||
B8:D3:09 CoxCommu Cox Communications, Inc
|
||||
B8:D4:3E vivoMobi vivo Mobile Communication Co., Ltd.
|
||||
B8:D4:9D MSevenSy M Seven System Ltd.
|
||||
|
@ -41158,6 +41220,7 @@ C4:32:D1 FarlinkT Farlink Technology Limited
|
|||
C4:33:06 ChinaMob China Mobile Group Device Co.,Ltd.
|
||||
C4:34:5B HuaweiTe Huawei Technologies Co.,Ltd
|
||||
C4:34:6B HewlettP Hewlett Packard
|
||||
C4:35:D9 Apple Apple, Inc.
|
||||
C4:36:55 Shenzhen Shenzhen Fenglian Technology Co., Ltd.
|
||||
C4:36:6C LGInnote LG Innotek
|
||||
C4:36:C0 Buffalo Buffalo.Inc
|
||||
|
@ -42145,6 +42208,7 @@ CC:B3:F8 FujitsuI Fujitsu Isotec Limited
|
|||
CC:B5:5A Fraunhof Fraunhofer ITWM
|
||||
CC:B5:D1 BeijingX Beijing Xiaomi Mobile Software Co., Ltd
|
||||
CC:B6:91 NECMagnu NECMagnusCommunications
|
||||
CC:B7:C4 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
CC:B8:88 AnBSecur AnB Securite s.a.
|
||||
CC:B8:A8 AMPAKTec AMPAK Technology, Inc.
|
||||
CC:B8:F1 EagleKin Eagle Kingdom Technologies Limited
|
||||
|
@ -42292,6 +42356,7 @@ D0:05:E4 HuaweiDe Huawei Device Co., Ltd.
|
|||
D0:06:6A Cornelis Cornelis Networks, Inc.
|
||||
D0:07:90 TexasIns Texas Instruments
|
||||
D0:07:CA JuniperN Juniper Networks
|
||||
D0:09:C8 Cisco Cisco Systems, Inc
|
||||
D0:0A:AB Yokogawa Yokogawa Digital Computer Corporation
|
||||
D0:0D:F7 HuaweiDe Huawei Device Co., Ltd.
|
||||
D0:0E:A4 PorscheC Porsche Cars North America
|
||||
|
@ -42366,6 +42431,7 @@ D0:35:E5 EMMicroe EM Microelectronic
|
|||
D0:37:42 YulongCo Yulong Computer Telecommunication Scientific (Shenzhen) Co.,Ltd
|
||||
D0:37:45 Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
D0:37:61 TexasIns Texas Instruments
|
||||
D0:39:57 LiteonTe Liteon Technology Corporation
|
||||
D0:39:72 TexasIns Texas Instruments
|
||||
D0:39:B3 ARRISGro ARRIS Group, Inc.
|
||||
D0:39:EA NetApp
|
||||
|
@ -42388,6 +42454,7 @@ D0:4C:C1 SINTRONE SINTRONES Technology Corp.
|
|||
D0:4D:2C Roku Roku, Inc.
|
||||
D0:4D:C6 ArubaaHe Aruba, a Hewlett Packard Enterprise Company
|
||||
D0:4E:50 Mobiwire Mobiwire Mobiles (NingBo) Co., LTD
|
||||
D0:4E:99 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
D0:4F:7E Apple Apple, Inc.
|
||||
D0:50:99 ASRockIn ASRock Incorporation
|
||||
D0:51:57 LEAXArki LEAX Arkivator Telecom
|
||||
|
@ -42767,6 +42834,7 @@ D4:36:DB JiangsuT Jiangsu Toppower Automotive Electronics Co., Ltd
|
|||
D4:37:D7 zte zte corporation
|
||||
D4:38:9C Sony Sony Corporation
|
||||
D4:39:B8 Ciena Ciena Corporation
|
||||
D4:3A:2C Google Google, Inc.
|
||||
D4:3A:2E Shenzhen Shenzhen Mtc Co Ltd
|
||||
D4:3A:65 IGRSEngi IGRS Engineering Lab Ltd.
|
||||
D4:3A:E9 DONGGUAN DONGGUAN ipt INDUSTRIAL CO., LTD
|
||||
|
@ -44837,6 +44905,7 @@ EC:14:F6 BioContr BioControl AS
|
|||
EC:15:3D BeijingY Beijing Yaxunhongda Technology Co., Ltd.
|
||||
EC:17:2F Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
EC:17:66 Research Research Centre Module
|
||||
EC:1A:02 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
EC:1A:59 BelkinIn Belkin International Inc.
|
||||
EC:1B:BD SiliconL Silicon Laboratories
|
||||
EC:1C:5D Siemens Siemens AG
|
||||
|
@ -45396,6 +45465,8 @@ F0:C2:7C Mianyang Mianyang Netop Telecom Equipment Co.,Ltd.
|
|||
F0:C3:71 Apple Apple, Inc.
|
||||
F0:C4:2F HuaweiDe Huawei Device Co., Ltd.
|
||||
F0:C4:78 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
F0:C7:25 Apple Apple, Inc.
|
||||
F0:C7:45 TecnoMob Tecno Mobile Limited
|
||||
F0:C7:7F TexasIns Texas Instruments
|
||||
F0:C8:14 Shenzhen Shenzhen Bilian Electronic Co.,Ltd
|
||||
F0:C8:50 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
|
@ -46204,7 +46275,7 @@ F8:C0:01 JuniperN Juniper Networks
|
|||
F8:C0:91 Highgate Highgates Technology
|
||||
F8:C1:16 JuniperN Juniper Networks
|
||||
F8:C1:20 XianLink Xi'an Link-Science Technology Co.,Ltd
|
||||
F8:C2:49 Private
|
||||
F8:C2:49 AmpereCo Ampere Computing Llc
|
||||
F8:C2:88 Cisco Cisco Systems, Inc
|
||||
F8:C3:72 TsuzukiD Tsuzuki Denki
|
||||
F8:C3:97 NZXT NZXT Corp. Ltd.
|
||||
|
@ -46238,6 +46309,7 @@ F8:DB:4C PNYTechn PNY Technologies, INC.
|
|||
F8:DB:7F HTC HTC Corporation
|
||||
F8:DB:88 Dell Dell Inc.
|
||||
F8:DC:7A Variscit Variscite LTD
|
||||
F8:DE:73 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
F8:DF:15 SunitecE Sunitec Enterprise Co.,Ltd
|
||||
F8:DF:A8 zte zte corporation
|
||||
F8:DF:E1 MyLight MyLight Systems
|
||||
|
@ -46264,6 +46336,7 @@ F8:ED:A5 ARRISGro ARRIS Group, Inc.
|
|||
F8:F0:05 NewportM Newport Media Inc.
|
||||
F8:F0:14 RackWare RackWare Inc.
|
||||
F8:F0:82 Nagtech Nagtech Llc
|
||||
F8:F0:C5 SuzhouKu Suzhou Kuhan Information Technologies Co.,Ltd.
|
||||
F8:F1:B6 Motorola Motorola Mobility LLC, a Lenovo Company
|
||||
F8:F1:E6 SamsungE Samsung Electronics Co.,Ltd
|
||||
F8:F2:1E IntelCor Intel Corporate
|
||||
|
|
|
@ -29,7 +29,7 @@
|
|||
</message>
|
||||
<message>
|
||||
<source>Copy to Clipboard</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>クリップボードへコピー</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Authors</source>
|
||||
|
@ -2231,19 +2231,19 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
</message>
|
||||
<message>
|
||||
<source>By default order comparisons and contains/matches/in relations are true if any value matches. The quantifier "all" can be used to apply the test to all values in a frame.</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>デフォルトでは比較演算子と contains/matches/in 関係演算子はいずれかの値が一致した場合に真になります。数量詞 "all" はフレーム内の全ての値に適用するテストに使えます。</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Quantifier</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>数量</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Any</source>
|
||||
<translation type="unfinished">すべて</translation>
|
||||
<translation>いずれかの</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>All</source>
|
||||
<translation type="unfinished">すべて</translation>
|
||||
<translation>すべて</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Match against this value.</source>
|
||||
|
@ -7904,7 +7904,7 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
</message>
|
||||
<message>
|
||||
<source>Any </source>
|
||||
<translation>すべて </translation>
|
||||
<translation>いずれかの</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Don't show this message again.</source>
|
||||
|
@ -10644,7 +10644,7 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
</message>
|
||||
<message>
|
||||
<source>Any</source>
|
||||
<translation>すべて</translation>
|
||||
<translation>いずれかの</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Network</source>
|
||||
|
|
|
@ -29,7 +29,7 @@
|
|||
</message>
|
||||
<message>
|
||||
<source>Copy to Clipboard</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Kopiera till urklipp</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Authors</source>
|
||||
|
@ -379,7 +379,7 @@
|
|||
</message>
|
||||
<message>
|
||||
<source>Ctrl+M</source>
|
||||
<translation type="unfinished">Ctrl+M</translation>
|
||||
<translation>Ctrl+M</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Mark/Unmark Cell</source>
|
||||
|
@ -723,7 +723,7 @@
|
|||
<name>ByteViewText</name>
|
||||
<message>
|
||||
<source>Allow hover highlighting</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Tillåt markering vid hovring</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Show bytes as hexadecimal</source>
|
||||
|
@ -1475,11 +1475,11 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
</message>
|
||||
<message>
|
||||
<source><html><head/><body><p>Optionally specify a temporary directory for unnamed capture files.</p></body></html></source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation><html><head/><body><p>Ange om så önskas en tillfällig katalog för namnlösa fångstfiler.</p></body></html></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Directory for temporary files</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Katalog för tillfälliga filer</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Capture Options</source>
|
||||
|
@ -1499,7 +1499,7 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
</message>
|
||||
<message>
|
||||
<source>Specify temporary directory</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Ange temporärkatalog</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>%1: %2</source>
|
||||
|
@ -1738,11 +1738,11 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
</message>
|
||||
<message>
|
||||
<source>Resolve Names:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Slå upp namn:</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source><html><head/><p>Show human-readable strings instead of raw values for fields. Only applicable to custom columns with fields that have value strings.</p></body></html></source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation><html><head/><p>Visa mänskligt läsbara strängar istället för råa värden för fält. Endast tillämpligt på anpassade kolumner med fält som har värdesträngar.</p></body></html></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Missing fields.</source>
|
||||
|
@ -1781,11 +1781,11 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
</message>
|
||||
<message>
|
||||
<source>Resolved</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Uppslagen</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source><html>Show human-readable strings instead of raw values for fields. Only applicable to custom columns with fields that have value strings.</html></source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation><html>Visa mänskligt läsbara strängar istället för råa värden för fält. Endast tillämpligt på anpassade kolumner med fält som har värdesträngar.</html></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>New Column</source>
|
||||
|
@ -1834,71 +1834,71 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
<name>ConversationDataModel</name>
|
||||
<message>
|
||||
<source>Address A</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Adress A</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Port A</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Port A</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Address B</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Adress B</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Port B</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Port B</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Packets</source>
|
||||
<translation type="unfinished">Paket</translation>
|
||||
<translation>Paket</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Bytes</source>
|
||||
<translation type="unfinished">Byte</translation>
|
||||
<translation>Byte</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Stream ID</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Ström-ID</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Packets A </source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Paket A</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Bytes A </source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Byte A</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Bytes B </source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Byte B</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Abs Start</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Abs start</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Rel Start</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Rel start</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Duration</source>
|
||||
<translation type="unfinished">Varaktighet</translation>
|
||||
<translation>Varaktighet</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Bits/s A </source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Bitar/s A</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Bits/s B </source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Bitar/s B</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Total Packets</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Totalt antal paket</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Percent Filtered</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Procent filtrerade</translation>
|
||||
</message>
|
||||
</context>
|
||||
<context>
|
||||
|
@ -2074,11 +2074,11 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
</message>
|
||||
<message>
|
||||
<source>Change behavior when the field matches this value</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Ändra beteenden när fältet matchar detta värde</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Field value type (and base, if Integer)</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Fältvärdetypen (och basen, ifall heltal)</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Current"Decode As" behavior</source>
|
||||
|
@ -2239,19 +2239,19 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
</message>
|
||||
<message>
|
||||
<source>By default order comparisons and contains/matches/in relations are true if any value matches. The quantifier "all" can be used to apply the test to all values in a frame.</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Som standard är ordningsjämförelser och innehåller-/matchar-/i-relationer sanna om något värde matchar. Kvantifieraren ”all” kan användas för att tillämpa testet på alla värden i en ram.</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Quantifier</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Kvantifierare</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Any</source>
|
||||
<translation type="unfinished">Godtycklig</translation>
|
||||
<translation>Något</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>All</source>
|
||||
<translation type="unfinished">Allt</translation>
|
||||
<translation>Alla</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Match against this value.</source>
|
||||
|
@ -2430,35 +2430,35 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
<name>EndpointDataModel</name>
|
||||
<message>
|
||||
<source>Address</source>
|
||||
<translation type="unfinished">Adress</translation>
|
||||
<translation>Adress</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Port</source>
|
||||
<translation type="unfinished">Port</translation>
|
||||
<translation>Port</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Packets</source>
|
||||
<translation type="unfinished">Paket</translation>
|
||||
<translation>Paket</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Bytes</source>
|
||||
<translation type="unfinished">Byte</translation>
|
||||
<translation>Byte</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Tx Packets</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Snd paket</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Tx Bytes</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Snd byte</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Rx Packets</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Mott paket</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Rx Bytes</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Mott byte</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Country</source>
|
||||
|
@ -2478,11 +2478,11 @@ Till exempel, använd 1 timma för att en ny fil skall skapas varje timma vid he
|
|||
</message>
|
||||
<message>
|
||||
<source>Total Packets</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation type="unfinished">Totalt antal paket</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Percent Filtered</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation type="unfinished">Procent filtrerade</translation>
|
||||
</message>
|
||||
</context>
|
||||
<context>
|
||||
|
|
|
@ -29,7 +29,7 @@
|
|||
</message>
|
||||
<message>
|
||||
<source>Copy to Clipboard</source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation>Panoya Kopyala</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Authors</source>
|
||||
|
|
Loading…
Reference in New Issue