forked from osmocom/wireshark
[Automatic update for 2022-01-02]
Update manuf, services enterprise numbers, translations, and other items.pespin/osmux-wip
parent
40256c64e0
commit
17e4032e81
3
AUTHORS
3
AUTHORS
|
@ -4097,6 +4097,7 @@ Apeksha Singhal <apeksha.singhal[AT]gmail.com>
|
|||
Arjen Zonneveld <arjen[AT]bz2.nl>
|
||||
Arkady Gilinsky <8351139-ark-g[AT]users.noreply.gitlab.com>
|
||||
Arkady Gilinsky <arkady.gilinsky[AT]harmonicinc.com>
|
||||
Armin Felder <Armin.Felder[AT]gmail.com>
|
||||
Arnd Hannemann <arnd[AT]arndnet.de>
|
||||
Arnout Vandecappelle (Essensium/Mind) <arnout[AT]mind.be>
|
||||
Artem Mygaiev <joculator[AT]gmail.com>
|
||||
|
@ -4175,6 +4176,7 @@ Christian Krump <christian.krump[AT]br-automation.com>
|
|||
Christian Lamparter <chunkeey[AT]googlemail.com>
|
||||
Christian M. Amsüss <chrysn[AT]fsfe.org>
|
||||
Christian Reusch <creusch[AT]crnetpackets.com>
|
||||
Christian Svensson <blue[AT]cmd.nu>
|
||||
Christian Tellefsen <chris-git[AT]tellefsen.net>
|
||||
Christian Ullrich <chris[AT]chrullrich.net>
|
||||
Christoph Burger-Scheidlin <mail[AT]christoph.burger-scheidlin.name>
|
||||
|
@ -4836,6 +4838,7 @@ Rémy Léone <remy.leone[AT]gmail.com>
|
|||
Saku Ytti <saku[AT]ytti.fi>
|
||||
Sam Cisneros <Sam.Cisneros15[AT]protonmail.com>
|
||||
Samiran Saha <ssahasamiran[AT]gmail.com>
|
||||
Samuel D. Leslie <sdl[AT]nexiom.net>
|
||||
Sandeep Dahiya <sdahiya[AT]gmail.com>
|
||||
Sander Steffann <sander[AT]steffann.nl>
|
||||
Sandip Mukherjee <mukherjee.sandy30[AT]gmail.com>
|
||||
|
|
47
NEWS
47
NEWS
|
@ -10,10 +10,14 @@ Wireshark 3.7.0 Release Notes
|
|||
|
||||
What’s New
|
||||
|
||||
• We no longer ship Windows Installer (.msi) packages for 32-bit
|
||||
Windows. Issue 17779[1]
|
||||
|
||||
• The PCRE2 library (https://www.pcre.org/) is now a required
|
||||
dependency to build Wireshark.
|
||||
|
||||
• A compiler with C11 support is required.
|
||||
• You must now have a compiler with C11 support in order to build
|
||||
Wireshark.
|
||||
|
||||
Many improvements have been made. See the “New and Updated Features”
|
||||
section below for more details.
|
||||
|
@ -53,10 +57,19 @@ Wireshark 3.7.0 Release Notes
|
|||
• Adds a new strict equality operator "===" or "all_eq". 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), in
|
||||
adittion to "~=" (introduced in Wireshark 3.6.0).
|
||||
addition to "~=" (introduced in Wireshark 3.6.0).
|
||||
|
||||
• Adds the aliases "any_eq" for "==" and "all_ne" for "!=".
|
||||
|
||||
• Date and time 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.
|
||||
|
||||
• 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.
|
||||
|
||||
• HTTP2 dissector now supports using fake headers to parse the
|
||||
DATAs of streams captured without first HEADERS frames of a
|
||||
long-lived stream (like gRPC streaming call which allows sending
|
||||
|
@ -70,6 +83,13 @@ Wireshark 3.7.0 Release Notes
|
|||
• Capture Options dialog contains same configuration icon as
|
||||
Welcome Screen. It is possible to configure interface there.
|
||||
|
||||
• Extcap dialog remembers password items during runtime therefore
|
||||
it is possible to run extcap multiple times in row. Passwords are
|
||||
never stored to disk.
|
||||
|
||||
• It is possible to set extcap passwords on cli for tshark and
|
||||
other cli tools.
|
||||
|
||||
New File Format Decoding Support
|
||||
|
||||
New Protocol Support
|
||||
|
@ -99,7 +119,7 @@ Wireshark 3.7.0 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[1] on the Wireshark web site.
|
||||
be found on the download page[2] on the Wireshark web site.
|
||||
|
||||
File Locations
|
||||
|
||||
|
@ -114,22 +134,23 @@ Wireshark 3.7.0 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[2] and on the
|
||||
Community support is available on Wireshark’s Q&A site[3] 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].
|
||||
for all of Wireshark’s mailing lists can be found on the web site[4].
|
||||
|
||||
Bugs and feature requests can be reported on the issue tracker[4].
|
||||
Bugs and feature requests can be reported on the issue tracker[5].
|
||||
|
||||
Frequently Asked Questions
|
||||
|
||||
A complete FAQ is available on the Wireshark web site[5].
|
||||
A complete FAQ is available on the Wireshark web site[6].
|
||||
|
||||
Last updated 2021-12-26 16:06:41 UTC
|
||||
Last updated 2022-01-02 16:06:46 UTC
|
||||
|
||||
References
|
||||
|
||||
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://www.wireshark.org/faq.html
|
||||
1. https://gitlab.com/wireshark/wireshark/-/issues/17779
|
||||
2. https://www.wireshark.org/download.html
|
||||
3. https://ask.wireshark.org/
|
||||
4. https://www.wireshark.org/lists/
|
||||
5. https://gitlab.com/wireshark/wireshark/-/issues
|
||||
6. https://www.wireshark.org/faq.html
|
||||
|
|
|
@ -99,7 +99,7 @@ fills up, *Dumpcap* will switch writing to the next file and so on.
|
|||
|
||||
The created filenames are based on the filename given with the *-w* option,
|
||||
the number of the file and on the creation date and time,
|
||||
e.g. outfile_00001_20210714120117.pcap, outfile_00002_20210714120523.pcap, ...
|
||||
e.g. outfile_00001_20220714120117.pcap, outfile_00002_20220714120523.pcap, ...
|
||||
|
||||
With the __files__ option it's also possible to form a "ring buffer".
|
||||
This will fill up new files until the number of files specified,
|
||||
|
|
|
@ -204,7 +204,7 @@ fills up, *TShark* will switch writing to the next file and so on.
|
|||
|
||||
The created filenames are based on the filename given with the *-w* option,
|
||||
the number of the file and on the creation date and time,
|
||||
e.g. outfile_00001_20210714120117.pcap, outfile_00002_20210714120523.pcap, ...
|
||||
e.g. outfile_00001_20220714120117.pcap, outfile_00002_20220714120523.pcap, ...
|
||||
|
||||
With the __files__ option it's also possible to form a "ring buffer".
|
||||
This will fill up new files until the number of files specified,
|
||||
|
@ -241,7 +241,7 @@ packets.
|
|||
|
||||
*nametimenum*:__value__ Choose between two save filename templates. If
|
||||
__value__ is 1, make running file number part before start time part; this is
|
||||
the original and default behaviour (e.g. log_00001_20210714164426.pcap). If
|
||||
the original and default behaviour (e.g. log_00001_20220714164426.pcap). If
|
||||
__value__ is greater than 1, make start time part before running number part
|
||||
(e.g. log_20210828164426_00001.pcap). The latter makes alphabetical sorting
|
||||
order equal to creation time order, and keeps related multiple file sets in
|
||||
|
|
|
@ -201,7 +201,7 @@ fills up, *Wireshark* will switch writing to the next file and so on.
|
|||
|
||||
The created filenames are based on the filename given with the *-w* flag,
|
||||
the number of the file and on the creation date and time,
|
||||
e.g. outfile_00001_20210714120117.pcap, outfile_00002_20210714120523.pcap, ...
|
||||
e.g. outfile_00001_20220714120117.pcap, outfile_00002_20220714120523.pcap, ...
|
||||
|
||||
With the __files__ option it's also possible to form a "ring buffer".
|
||||
This will fill up new files until the number of files specified,
|
||||
|
@ -1137,7 +1137,7 @@ menu:File[File Set,List Files]::
|
|||
Show a dialog box that lists all files of the file set matching the currently
|
||||
loaded file. A file set is a compound of files resulting from a capture using
|
||||
the "multiple files" / "ringbuffer" mode, recognizable by the filename pattern,
|
||||
e.g.: Filename_00001_20210714101530.pcap.
|
||||
e.g.: Filename_00001_20220714101530.pcap.
|
||||
--
|
||||
|
||||
menu:File[File Set,Next File]::
|
||||
|
|
|
@ -488,8 +488,8 @@ Information about the folders used for capture files can be found in
|
|||
|File Name|“Create a new file...”|“Use a ring buffer...”|Mode|Resulting filename(s) used
|
||||
|-|-|-|Single temporary file|wiresharkXXXXXX (where XXXXXX is a unique number)
|
||||
|foo.cap|-|-|Single named file|foo.cap
|
||||
|foo.cap|x|-|Multiple files, continuous|foo_00001_20210714110102.cap, foo_00002_20210714110318.cap, ...
|
||||
|foo.cap|x|x|Multiple files, ring buffer|foo_00001_20210714110102.cap, foo_00002_20210714110318.cap, ...
|
||||
|foo.cap|x|-|Multiple files, continuous|foo_00001_20220714110102.cap, foo_00002_20220714110318.cap, ...
|
||||
|foo.cap|x|x|Multiple files, ring buffer|foo_00001_20220714110102.cap, foo_00002_20220714110318.cap, ...
|
||||
|===
|
||||
|
||||
Single temporary file::
|
||||
|
|
|
@ -691,7 +691,7 @@ some features to handle these file sets in a convenient way.
|
|||
.How does Wireshark detect the files of a file set?
|
||||
****
|
||||
A filename in a file set uses the format Prefix_Number_DateTimeSuffix which
|
||||
might look something like `test_00001_20210714183910.pcap`. All files of a file
|
||||
might look something like `test_00001_20220714183910.pcap`. All files of a file
|
||||
set share the same prefix (e.g. “test”) and suffix (e.g. “.pcap”) and a
|
||||
varying middle part.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Dumpcap (Wireshark) 3.7.0 (v3.7.0rc0-33-g0d276b47d120)
|
||||
Dumpcap (Wireshark) 3.7.0 (v3.7.0rc0-906-g40256c64e098)
|
||||
Capture network packets and dump them into a pcapng or pcap file.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
@ -68,6 +68,7 @@ Diagnostic output:
|
|||
--log-debug <[!]list> comma separated list of domains with "debug" level
|
||||
--log-noisy <[!]list> comma separated list of domains with "noisy" level
|
||||
--log-file <path> file to output messages to (in addition to stderr)
|
||||
|
||||
Miscellaneous:
|
||||
-N <packet_limit> maximum number of packets buffered within dumpcap
|
||||
-C <byte_limit> maximum number of bytes used for buffering packets
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Rawshark (Wireshark) 3.7.0 (v3.7.0rc0-33-g0d276b47d120)
|
||||
Rawshark (Wireshark) 3.7.0 (v3.7.0rc0-906-g40256c64e098)
|
||||
Dump and analyze network traffic.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
@ -24,6 +24,7 @@ Output:
|
|||
-S format string for fields
|
||||
(%D - name, %S - stringval, %N numval)
|
||||
-t ad|a|r|d|dd|e output format of time stamps (def: r: rel. to first)
|
||||
|
||||
Diagnostic output:
|
||||
--log-level <level> sets the active log level ("critical", "warning", etc.)
|
||||
--log-fatal <level> sets level to abort the program ("critical" or "warning")
|
||||
|
@ -32,6 +33,7 @@ Diagnostic output:
|
|||
--log-noisy <[!]list> comma separated list of domains with "noisy" level
|
||||
--log-file <path> file to output messages to (in addition to stderr)
|
||||
|
||||
|
||||
Miscellaneous:
|
||||
-h display this help and exit
|
||||
-o <name>:<value> ... override preference setting
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Text2pcap (Wireshark) 3.7.0 (v3.7.0rc0-826-gb3215d99cacb)
|
||||
Text2pcap (Wireshark) 3.7.0 (v3.7.0rc0-906-g40256c64e098)
|
||||
Generate a capture file from an ASCII hexdump of packets.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
@ -20,14 +20,25 @@ Input:
|
|||
used as the default for unspecified fields.
|
||||
-D the text before the packet starts with an I or an O,
|
||||
indicating that the packet is inbound or outbound.
|
||||
This is used when generating dummy headers.
|
||||
The indication is only stored if the output format is pcapng.
|
||||
This is used when generating dummy headers if the
|
||||
output format supports it (e.g. pcapng).
|
||||
-a enable ASCII text dump identification.
|
||||
The start of the ASCII text dump can be identified
|
||||
and excluded from the packet data, even if it looks
|
||||
like a HEX dump.
|
||||
NOTE: Do not enable it if the input file does not
|
||||
contain the ASCII text dump.
|
||||
-r <regex> enable regex mode. Scan the input using <regex>, a Perl
|
||||
compatible regular expression matching a single packet.
|
||||
Named capturing subgroups are used to identify fields:
|
||||
<data> (mand.), and <time>, <dir>, and <seqno> (opt.)
|
||||
The time field format is taken from the -t option
|
||||
Example: -r '^(?<dir>[<>])\s(?<time>\d+:\d\d:\d\d.\d+)\s(?<data>[0-9a-fA-F]+)$'
|
||||
could match a file with lines like
|
||||
> 0:00:00.265620 a130368b000000080060
|
||||
< 0:00:00.295459 a2010800000000000000000800000000
|
||||
-b 2|8|16|64 encoding base (radix) of the packet data in regex mode
|
||||
(def: 16: hexadecimal) No effect in hexdump mode.
|
||||
|
||||
Output:
|
||||
-l <typenum> link-layer type number; default is 1 (Ethernet). See
|
||||
|
@ -73,8 +84,20 @@ Prepend dummy header:
|
|||
chunk header with payload protocol identifier ppi.
|
||||
Example: -S 30,40,34
|
||||
|
||||
-P <dissector> prepend EXPORTED_PDU header with specifieddissector
|
||||
as the payload PROTO_NAME tag.
|
||||
Automatically sets link type to Upper PDU Export.
|
||||
EXPORTED_PDU payload defaults to "data" otherwise.
|
||||
|
||||
Diagnostic output:
|
||||
--log-level <level> sets the active log level ("critical", "warning", etc.)
|
||||
--log-fatal <level> sets level to abort the program ("critical" or "warning")
|
||||
--log-domains <[!]list> comma separated list of the active log domains
|
||||
--log-debug <[!]list> comma separated list of domains with "debug" level
|
||||
--log-noisy <[!]list> comma separated list of domains with "noisy" level
|
||||
--log-file <path> file to output messages to (in addition to stderr)
|
||||
|
||||
Miscellaneous:
|
||||
-h display this help and exit.
|
||||
-v print version information and exit.
|
||||
-d show detailed debug of parser states.
|
||||
-q generate no output at all (automatically disables -d).
|
||||
-h display this help and exit
|
||||
-v print version information and exit
|
||||
-q don't report processed packet counts
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
TShark (Wireshark) 3.7.0 (v3.7.0rc0-33-g0d276b47d120)
|
||||
TShark (Wireshark) 3.7.0 (v3.7.0rc0-906-g40256c64e098)
|
||||
Dump and analyze network traffic.
|
||||
See https://www.wireshark.org for more information.
|
||||
|
||||
|
@ -125,6 +125,7 @@ Output:
|
|||
values
|
||||
--elastic-mapping-filter <protocols> If -G elastic-mapping is specified, put only the
|
||||
specified protocols within the mapping file
|
||||
|
||||
Diagnostic output:
|
||||
--log-level <level> sets the active log level ("critical", "warning", etc.)
|
||||
--log-fatal <level> sets level to abort the program ("critical" or "warning")
|
||||
|
|
|
@ -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 2021-12-24)
|
||||
# (last updated 2022-01-01)
|
||||
|
||||
0 Reserved
|
||||
1 NxNetworks
|
||||
|
@ -47116,7 +47116,7 @@
|
|||
47297 hotelleriesuisse
|
||||
47298 Pastem Solutions, Ltd.
|
||||
47299 P2 Wireless Technologies Limited
|
||||
47300 itelligence AG
|
||||
47300 NTT DATA Business Solutions AG
|
||||
47301 "NR"WEB US
|
||||
47302 Alnatura Produktions- und Handels GmbH
|
||||
47303 Moratua Solutions
|
||||
|
@ -58066,3 +58066,23 @@
|
|||
58273 Cellhire plc
|
||||
58274 HILO.CZ
|
||||
58275 Eternalplanet Energy Ltd
|
||||
58276 Bundeskriminalamt
|
||||
58277 Insite360
|
||||
58278 Adopt Nettech Pvt Ltd
|
||||
58279 Peer Software, Inc.
|
||||
58280 Grassie
|
||||
58281 Allianz Technology SE
|
||||
58282 Zethe
|
||||
58283 BIPBIP365
|
||||
58284 Juuso Marttinen
|
||||
58285 Connor Goodwolf
|
||||
58286 harada syouten
|
||||
58287 bpm consult ag
|
||||
58288 Digital Workplace 360 GmbH
|
||||
58289 FABMation GmbH
|
||||
58290 Guangzhou GRG Wuzhou Technology Co., Ltd.
|
||||
58291 Direction Générale des Finances publiques
|
||||
58292 Satish A Shah MD PLLC
|
||||
58293 Uptime-ICT
|
||||
58294 Copper River Seafoods
|
||||
58295 X-Pert Multimedia Solutions Ltd.
|
||||
|
|
Can't render this file because it is too large.
|
File diff suppressed because it is too large
Load Diff
|
@ -6,8 +6,8 @@
|
|||
*
|
||||
* List of PCI ID's
|
||||
*
|
||||
* Version: 2021.12.25
|
||||
* Date: 2021-12-25 03:15:02
|
||||
* Version: 2021.12.31
|
||||
* Date: 2021-12-31 03:15:01
|
||||
*
|
||||
* Maintained by Albert Pool, Martin Mares, and other volunteers from
|
||||
* the PCI ID Project at https://pci-ids.ucw.cz/.
|
||||
|
@ -13023,9 +13023,12 @@ pci_id_t pci_vid_10DE[] = {
|
|||
{0x10DE, 0x1FB9, 0xFFFF, 0xFFFF, "TU117GLM [Quadro T1000 Mobile](0x1FB9)"},
|
||||
{0x10DE, 0x1FBA, 0xFFFF, 0xFFFF, "TU117GLM [T600 Mobile](0x1FBA)"},
|
||||
{0x10DE, 0x1FBB, 0xFFFF, 0xFFFF, "TU117GLM [Quadro T500 Mobile](0x1FBB)"},
|
||||
{0x10DE, 0x1FBC, 0xFFFF, 0xFFFF, "TU117GLM [T1200 Laptop GPU](0x1FBC)"},
|
||||
{0x10DE, 0x1FBF, 0xFFFF, 0xFFFF, "TU117GL(0x1FBF)"},
|
||||
{0x10DE, 0x1FD9, 0xFFFF, 0xFFFF, "TU117BM [GeForce GTX 1650 Mobile Refresh](0x1FD9)"},
|
||||
{0x10DE, 0x1FDD, 0xFFFF, 0xFFFF, "TU117BM [GeForce GTX 1650 Mobile Refresh](0x1FDD)"},
|
||||
{0x10DE, 0x1FF0, 0xFFFF, 0xFFFF, "TU117GL [T1000 8GB](0x1FF0)"},
|
||||
{0x10DE, 0x1FF2, 0xFFFF, 0xFFFF, "TU117GL [T400 4GB](0x1FF2)"},
|
||||
{0x10DE, 0x1FF9, 0xFFFF, 0xFFFF, "TU117GLM [Quadro T1000 Mobile](0x1FF9)"},
|
||||
{0x10DE, 0x20B0, 0xFFFF, 0xFFFF, "GA100 [A100 SXM4 40GB](0x20B0)"},
|
||||
{0x10DE, 0x20B1, 0xFFFF, 0xFFFF, "GA100 [A100 PCIe 40GB](0x20B1)"},
|
||||
|
@ -24843,6 +24846,7 @@ pci_id_t pci_vid_15B3[] = {
|
|||
{0x15B3, 0x0256, 0xFFFF, 0xFFFF, "Abir GearBox(0x0256)"},
|
||||
{0x15B3, 0x0257, 0xFFFF, 0xFFFF, "Quantum-2 in Flash Recovery Mode(0x0257)"},
|
||||
{0x15B3, 0x0258, 0xFFFF, 0xFFFF, "Quantum-2 RMA(0x0258)"},
|
||||
{0x15B3, 0x0259, 0xFFFF, 0xFFFF, "Abir Chiplet(0x0259)"},
|
||||
{0x15B3, 0x0262, 0xFFFF, 0xFFFF, "MT27710 [ConnectX-4 Lx Programmable] EN(0x0262)"},
|
||||
{0x15B3, 0x0263, 0xFFFF, 0xFFFF, "MT27710 [ConnectX-4 Lx Programmable Virtual Function] EN(0x0263)"},
|
||||
{0x15B3, 0x0264, 0xFFFF, 0xFFFF, "Innova-2 Flex Burn image(0x0264)"},
|
||||
|
@ -29690,6 +29694,8 @@ pci_id_t pci_vid_1DE5[] = {
|
|||
|
||||
pci_id_t pci_vid_1DED[] = {
|
||||
{0x1DED, 0xFFFF, 0xFFFF, 0xFFFF, "Alibaba (China) Co., Ltd.(0x1DED)"},
|
||||
{0x1DED, 0x107F, 0xFFFF, 0xFFFF, "Elastic RDMA Adapter(0x107F)"},
|
||||
{0x1DED, 0x5007, 0xFFFF, 0xFFFF, "Elastic RDMA Adapter(0x5007)"},
|
||||
{0x1DED, 0x8000, 0xFFFF, 0xFFFF, "M1 Root Port(0x8000)"},
|
||||
{0x1DED, 0x8001, 0xFFFF, 0xFFFF, "ACC-RCiEP(0x8001)"},
|
||||
{0x1DED, 0x8002, 0xFFFF, 0xFFFF, "RCiEP VF(0x8002)"},
|
||||
|
@ -37850,8 +37856,10 @@ pci_id_t pci_vid_8086[] = {
|
|||
{0x8086, 0x43F0, 0x8086, 0x02A4, "Wireless-AC 9462(0x8086-0x02A4)"},
|
||||
{0x8086, 0x444E, 0xFFFF, 0xFFFF, "Turbo Memory Controller(0x444E)"},
|
||||
{0x8086, 0x460D, 0xFFFF, 0xFFFF, "12th Gen Core Processor PCI Express x16 Controller #1(0x460D)"},
|
||||
{0x8086, 0x461D, 0xFFFF, 0xFFFF, "Alder Lake Innovation Platform Framework Processor Participant(0x461D)"},
|
||||
{0x8086, 0x461E, 0xFFFF, 0xFFFF, "Alder Lake-P Thunderbolt 4 USB Controller(0x461E)"},
|
||||
{0x8086, 0x461F, 0xFFFF, 0xFFFF, "Alder Lake-P Thunderbolt 4 PCI Express Root Port #3(0x461F)"},
|
||||
{0x8086, 0x4626, 0xFFFF, 0xFFFF, "Alder Lake-P Integrated Graphics Controller(0x4626)"},
|
||||
{0x8086, 0x4629, 0xFFFF, 0xFFFF, "12th Gen Core Processor Host Bridge/DRAM Registers(0x4629)"},
|
||||
{0x8086, 0x462F, 0xFFFF, 0xFFFF, "Alder Lake-P Thunderbolt 4 PCI Express Root Port #2(0x462F)"},
|
||||
{0x8086, 0x463D, 0xFFFF, 0xFFFF, "12th Gen Core Processor PCI Express x4 Controller #2(0x463D)"},
|
||||
|
@ -40967,7 +40975,7 @@ pci_vid_index_t pci_vid_index[] = {
|
|||
{0x10DB, 1, pci_vid_10DB },
|
||||
{0x10DC, 6, pci_vid_10DC },
|
||||
{0x10DD, 3, pci_vid_10DD },
|
||||
{0x10DE, 3079, pci_vid_10DE },
|
||||
{0x10DE, 3082, pci_vid_10DE },
|
||||
{0x10DF, 122, pci_vid_10DF },
|
||||
{0x10E0, 7, pci_vid_10E0 },
|
||||
{0x10E1, 5, pci_vid_10E1 },
|
||||
|
@ -42172,7 +42180,7 @@ pci_vid_index_t pci_vid_index[] = {
|
|||
{0x15B0, 1, pci_vid_15B0 },
|
||||
{0x15B1, 1, pci_vid_15B1 },
|
||||
{0x15B2, 1, pci_vid_15B2 },
|
||||
{0x15B3, 232, pci_vid_15B3 },
|
||||
{0x15B3, 233, pci_vid_15B3 },
|
||||
{0x15B4, 1, pci_vid_15B4 },
|
||||
{0x15B5, 1, pci_vid_15B5 },
|
||||
{0x15B6, 17, pci_vid_15B6 },
|
||||
|
@ -42683,7 +42691,7 @@ pci_vid_index_t pci_vid_index[] = {
|
|||
{0x1DE0, 2, pci_vid_1DE0 },
|
||||
{0x1DE1, 5, pci_vid_1DE1 },
|
||||
{0x1DE5, 4, pci_vid_1DE5 },
|
||||
{0x1DED, 6, pci_vid_1DED },
|
||||
{0x1DED, 8, pci_vid_1DED },
|
||||
{0x1DEE, 1, pci_vid_1DEE },
|
||||
{0x1DEF, 27, pci_vid_1DEF },
|
||||
{0x1DF3, 29, pci_vid_1DF3 },
|
||||
|
@ -42856,7 +42864,7 @@ pci_vid_index_t pci_vid_index[] = {
|
|||
{0x7FED, 1, pci_vid_7FED },
|
||||
{0x8008, 4, pci_vid_8008 },
|
||||
{0x807D, 1, pci_vid_807D },
|
||||
{0x8086, 8156, pci_vid_8086 },
|
||||
{0x8086, 8158, pci_vid_8086 },
|
||||
{0x8088, 51, pci_vid_8088 },
|
||||
{0x80EE, 3, pci_vid_80EE },
|
||||
{0x8322, 1, pci_vid_8322 },
|
||||
|
|
73
manuf
73
manuf
|
@ -44,24 +44,24 @@
|
|||
# https://gitlab.com/wireshark/wireshark/-/raw/master/manuf
|
||||
|
||||
# http://standards-oui.ieee.org/cid/cid.csv:
|
||||
# Content-Length: 11619
|
||||
# Last-Modified: Sun, 26 Dec 2021 15:00:21 GMT
|
||||
# Content-Length: 11744
|
||||
# Last-Modified: Sun, 02 Jan 2022 15:00:36 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/iab/iab.csv:
|
||||
# Content-Length: 381494
|
||||
# Last-Modified: Sun, 26 Dec 2021 15:00:34 GMT
|
||||
# Last-Modified: Sun, 02 Jan 2022 15:00:51 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/oui/oui.csv:
|
||||
# Content-Length: 2875464
|
||||
# Last-Modified: Sun, 26 Dec 2021 15:01:09 GMT
|
||||
# Content-Length: 2880044
|
||||
# Last-Modified: Sun, 02 Jan 2022 15:01:31 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/oui28/mam.csv:
|
||||
# Content-Length: 435817
|
||||
# Last-Modified: Sun, 26 Dec 2021 15:00:43 GMT
|
||||
# Content-Length: 437237
|
||||
# Last-Modified: Sun, 02 Jan 2022 15:01:01 GMT
|
||||
|
||||
# http://standards-oui.ieee.org/oui36/oui36.csv:
|
||||
# Content-Length: 423047
|
||||
# Last-Modified: Sun, 26 Dec 2021 15:01:02 GMT
|
||||
# Content-Length: 423683
|
||||
# Last-Modified: Sun, 02 Jan 2022 15:01:23 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
|
||||
|
@ -4035,7 +4035,7 @@
|
|||
00:0F:9D DisplayL DisplayLink (UK) Ltd
|
||||
00:0F:9E Murrelek Murrelektronik GmbH
|
||||
00:0F:9F ARRISGro ARRIS Group, Inc.
|
||||
00:0F:A0 CanonKor Canon Korea Business Solutions Inc.
|
||||
00:0F:A0 CanonKor Canon Korea Inc.
|
||||
00:0F:A1 Gigabit Gigabit Systems Inc.
|
||||
00:0F:A2 2xWirele 2xWireless
|
||||
00:0F:A3 AlphaNet Alpha Networks Inc.
|
||||
|
@ -16344,6 +16344,7 @@
|
|||
00:A0:FE BostonTe Boston Technology, Inc.
|
||||
00:A0:FF TellabsO Tellabs Operations, Inc.
|
||||
00:A1:DE ShenZhen ShenZhen ShiHua Technology CO.,LTD
|
||||
00:A2:65 M2Motive M2Motive Technology Inc.
|
||||
00:A2:89 Cisco Cisco Systems, Inc
|
||||
00:A2:DA INAT INAT GmbH
|
||||
00:A2:EE Cisco Cisco Systems, Inc
|
||||
|
@ -18374,6 +18375,16 @@
|
|||
0C:84:DC HonHaiPr Hon Hai Precision Ind. Co.,Ltd.
|
||||
0C:85:25 Cisco Cisco Systems, Inc
|
||||
0C:86:10 JuniperN Juniper Networks
|
||||
0C:86:29 IEEERegi IEEE Registration Authority
|
||||
0C:86:29:00:00:00/28 Shanghai Shanghai Prophet Electronic Technology Co.,Ltd
|
||||
0C:86:29:10:00:00/28 BeijingQ Beijing Qinmu Data Technology Co., Ltd.
|
||||
0C:86:29:20:00:00/28 BADASYST BADA SYSTEM co., Ltd
|
||||
0C:86:29:50:00:00/28 Shenzhen Shenzhen protostellar technology Co., Ltd
|
||||
0C:86:29:60:00:00/28 C&AMarke C&A Marketing, INC.
|
||||
0C:86:29:90:00:00/28 Hongkong Hongkong Saint Tech Industrial Limited
|
||||
0C:86:29:A0:00:00/28 Nipron Nipron Co.,Ltd
|
||||
0C:86:29:C0:00:00/28 Shenzhen Shenzhen Yingmu Technology.,Ltd
|
||||
0C:86:29:D0:00:00/28 BeijingB Beijing Beibianzhida Technology Co.,Ltd
|
||||
0C:89:10 SamsungE Samsung Electronics Co.,Ltd
|
||||
0C:8A:87 AgLogica AgLogica Holdings, Inc
|
||||
0C:8B:7D Vizio Vizio, Inc
|
||||
|
@ -18667,6 +18678,7 @@
|
|||
10:49:63 Harting Harting K.K.
|
||||
10:4A:7D IntelCor Intel Corporate
|
||||
10:4B:46 Mitsubis Mitsubishi Electric Corporation
|
||||
10:4D:15 Viaanix Viaanix Inc
|
||||
10:4D:77 Innovati Innovative Computer Engineering
|
||||
10:4E:07 Shanghai Shanghai Genvision Industries Co.,Ltd
|
||||
10:4E:89 GarminIn Garmin International
|
||||
|
@ -18684,6 +18696,7 @@
|
|||
10:54:D2:30:00:00/28 LittleAr Little Array Technology (Shenzhen) Co., Ltd.
|
||||
10:54:D2:40:00:00/28 Raylogic Raylogic Control Systems Private Limited
|
||||
10:54:D2:50:00:00/28 Sybersen Sybersense
|
||||
10:54:D2:60:00:00/28 LanaoCom Lanao Communication Technology Limited
|
||||
10:54:D2:70:00:00/28 Shenzhen Shenzhen Carsafe Technology Development Co.,Ltd
|
||||
10:54:D2:80:00:00/28 Annapurn Annapurna labs
|
||||
10:54:D2:90:00:00/28 BambooDy Bamboo Dynamics Corporation., Ltd.
|
||||
|
@ -18691,6 +18704,7 @@
|
|||
10:54:D2:B0:00:00/28 Shenzhen Shenzhen Dinstech Technology Co.,Ltd.
|
||||
10:54:D2:C0:00:00/28 LUXSHARE LUXSHARE-ICT Co., Ltd.
|
||||
10:54:D2:D0:00:00/28 Sunwealt Sun wealth technology corporation limited
|
||||
10:54:D2:E0:00:00/28 CosmoAio Cosmo Aiot Technology Co Ltd
|
||||
10:55:E4 Shenzhen Shenzhen Skyworth Digital Technology CO., Ltd
|
||||
10:56:11 ARRISGro ARRIS Group, Inc.
|
||||
10:56:CA PeplinkI Peplink International Ltd.
|
||||
|
@ -18711,6 +18725,7 @@
|
|||
10:62:D0 Technico Technicolor CH USA Inc.
|
||||
10:62:E5 HewlettP Hewlett Packard
|
||||
10:62:EB D-LinkIn D-Link International
|
||||
10:63:4B Shenzhen Shenzhen Mercury Communication Technologies Co.,Ltd.
|
||||
10:63:C8 LiteonTe Liteon Technology Corporation
|
||||
10:64:E2 ADFwebco ADFweb.com s.r.l.
|
||||
10:65:30 Dell Dell Inc.
|
||||
|
@ -19064,6 +19079,7 @@
|
|||
14:6E:0A Private
|
||||
14:73:73 TubitakU Tubitak Uekae
|
||||
14:74:11 Rim
|
||||
14:75:5B IntelCor Intel Corporate
|
||||
14:75:90 Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
14:77:40 HuaweiDe Huawei Device Co., Ltd.
|
||||
14:78:0B VarexIma Varex Imaging Deutschland AG
|
||||
|
@ -19710,6 +19726,7 @@
|
|||
1C:45:93 TexasIns Texas Instruments
|
||||
1C:45:C2 HuizhouC Huizhou City Sunsin lntelligent Technology Co.,Ltd
|
||||
1C:47:2F HuaweiDe Huawei Device Co., Ltd.
|
||||
1C:47:F6 ZhidaoNe Zhidao Network Technology(Shenzhen) Co.,Ltd
|
||||
1C:48:40 IMSMesss IMS Messsysteme GmbH
|
||||
1C:48:CE Guangdon Guangdong Oppo Mobile Telecommunications Corp.,Ltd
|
||||
1C:48:F9 GNNetcom GN Netcom A/S
|
||||
|
@ -20267,7 +20284,9 @@
|
|||
20:89:6F Fiberhom Fiberhome Telecommunication Technologies Co.,LTD
|
||||
20:89:84 CompalIn Compal Information (Kunshan) Co., Ltd.
|
||||
20:89:86 zte zte corporation
|
||||
20:89:8A Shenzhen Shenzhen Skyworth Digital Technology CO., Ltd
|
||||
20:8B:37 Skyworth Skyworth Digital Technology(Shenzhen) Co.,Ltd
|
||||
20:8B:D1 NXPSemic NXP Semiconductor (Tianjin) LTD.
|
||||
20:8C:47 Tenstorr Tenstorrent Inc
|
||||
20:8C:86 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
20:90:6F Shenzhen Shenzhen Tencent Computer System Co., Ltd.
|
||||
|
@ -20933,6 +20952,7 @@
|
|||
28:A1:EB EtekTech Etek Technology (Shenzhen) Co.,Ltd
|
||||
28:A2:41 exlar exlar corp
|
||||
28:A2:4B JuniperN Juniper Networks
|
||||
28:A5:3F vivoMobi vivo Mobile Communication Co., Ltd.
|
||||
28:A5:74 MillerEl Miller Electric Mfg. Co.
|
||||
28:A5:EE Shenzhen Shenzhen SDGI CATV Co., Ltd
|
||||
28:A6:AC seca seca gmbh & co. kg
|
||||
|
@ -21115,6 +21135,7 @@
|
|||
2C:06:23 WinLeade Win Leader Inc.
|
||||
2C:07:3C Devline Devline Limited
|
||||
2C:07:86 HuaweiDe Huawei Device Co., Ltd.
|
||||
2C:07:F6 WearFutu Wear Future Technologies Co., Ltd.
|
||||
2C:08:1C Ovh
|
||||
2C:08:23 SercommF Sercomm France Sarl
|
||||
2C:08:8C HUMAX HUMAX Co., Ltd.
|
||||
|
@ -21565,6 +21586,7 @@
|
|||
30:27:CF Private
|
||||
30:29:52 Hillston Hillstone Networks Inc
|
||||
30:29:BE Shanghai Shanghai MRDcom Co.,Ltd
|
||||
30:2B:DC Top-Unum Top-Unum Electronics Co., LTD
|
||||
30:2D:E8 JDAJDA JDA, LLC (JDA Systems)
|
||||
30:31:7D Hosiden Hosiden Corporation
|
||||
30:32:35 QingdaoI Qingdao Intelligent&Precise Electronics Co.,Ltd.
|
||||
|
@ -22331,6 +22353,7 @@
|
|||
38:67:93 AsiaOpti Asia Optical Co., Inc.
|
||||
38:68:93 IntelCor Intel Corporate
|
||||
38:68:A4 SamsungE Samsung Electronics Co.,LTD
|
||||
38:68:BE SichuanT Sichuan Tianyi Comheart Telecom Co.,LTD
|
||||
38:68:DD Inventec Inventec Corporation
|
||||
38:6A:77 SamsungE Samsung Electronics Co.,Ltd
|
||||
38:6B:1C Shenzhen Shenzhen Mercury Communication Technologies Co.,Ltd.
|
||||
|
@ -25094,6 +25117,7 @@
|
|||
50:9F:27 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
50:9F:3B OiElectr Oi Electric Co.,Ltd
|
||||
50:A0:09 XiaomiCo Xiaomi Communications Co Ltd
|
||||
50:A0:15 Shenzhen Shenzhen Yipingfang Network Technology Co., Ltd.
|
||||
50:A0:30:00:00:00/28 GopodGro Gopod Group Limited
|
||||
50:A0:30:10:00:00/28 XEPIC XEPIC Corporation Limited
|
||||
50:A0:30:20:00:00/28 Annapurn Annapurna labs
|
||||
|
@ -25156,6 +25180,7 @@
|
|||
50:BD:5F Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
50:C0:06 Carmanah Carmanah Signs
|
||||
50:C0:F0 ArtekMic Artek Microelectronics Co.,Ltd.
|
||||
50:C1:F0 NXPSemic NXP Semiconductor (Tianjin) LTD.
|
||||
50:C2:71 Securete Securetech Inc
|
||||
50:C2:75 GNAudio GN Audio A/S
|
||||
50:C2:E8 CloudNet Cloud Network Technology Singapore Pte. Ltd.
|
||||
|
@ -25583,6 +25608,7 @@
|
|||
58:0A:D4 Apple Apple, Inc.
|
||||
58:10:8C Intelbra Intelbras
|
||||
58:10:B7 Infinixm Infinix mobility limited
|
||||
58:11:22 ASUSTekC ASUSTek COMPUTER INC.
|
||||
58:12:43 AcSiPTec AcSiP Technology Corp.
|
||||
58:13:D3 GemtekTe Gemtek Technology Co., Ltd.
|
||||
58:16:26 Avaya Avaya Inc
|
||||
|
@ -26111,6 +26137,7 @@
|
|||
5C:C2:13 FrSauter Fr. Sauter AG
|
||||
5C:C3:07 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
5C:C3:36 ittim
|
||||
5C:C5:63 HunanFn- Hunan Fn-Link Technology Limited
|
||||
5C:C5:D4 IntelCor Intel Corporate
|
||||
5C:C6:D0 Skyworth Skyworth Digital Technology(Shenzhen) Co.,Ltd
|
||||
5C:C6:E9 EdifierI Edifier International
|
||||
|
@ -27240,6 +27267,7 @@
|
|||
6C:22:AB Ainswort Ainsworth Game Technology
|
||||
6C:23:B9 Sony Sony Corporation
|
||||
6C:23:CB Wattty Wattty Corporation
|
||||
6C:24:08 LCFCHefe LCFC(Hefei) Electronics Technology Co., Ltd
|
||||
6C:24:83 Microsof Microsoft Mobile Oy
|
||||
6C:24:A6 vivoMobi vivo Mobile Communication Co., Ltd.
|
||||
6C:25:B9 BbkEduca Bbk Educational Electronics Corp.,Ltd.
|
||||
|
@ -27412,6 +27440,7 @@
|
|||
6C:AF:15 WebastoS Webasto SE
|
||||
6C:B0:CE Netgear
|
||||
6C:B0:FD Shenzhen Shenzhen Xinghai Iot Technology Co.,Ltd
|
||||
6C:B1:58 Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
6C:B2:27 SonyVide Sony Video & Sound Products Inc.
|
||||
6C:B2:AE Cisco Cisco Systems, Inc
|
||||
6C:B3:11 Shenzhen Shenzhen Lianrui Electronics Co.,Ltd
|
||||
|
@ -31959,6 +31988,7 @@
|
|||
74:03:BD Buffalo Buffalo.Inc
|
||||
74:04:2B LenovoMo Lenovo Mobile Communication (Wuhan) Company Limited
|
||||
74:04:F0 Mobiwire Mobiwire Mobiles (NingBo) Co., LTD
|
||||
74:04:F1 IntelCor Intel Corporate
|
||||
74:05:A5 Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
74:09:AC Quext Quext, LLC
|
||||
74:0A:BC Lightwav LightwaveRF Technology Ltd
|
||||
|
@ -32103,6 +32133,7 @@
|
|||
74:65:D1 Atlinks
|
||||
74:66:30 TmiYtti T:mi Ytti
|
||||
74:67:F7 ExtremeN Extreme Networks, Inc.
|
||||
74:69:4A SichuanT Sichuan Tianyi Comheart Telecom Co.,LTD
|
||||
74:6A:3A Aperi Aperi Corporation
|
||||
74:6A:89 Rezolt Rezolt Corporation
|
||||
74:6A:8F VSVision VS Vision Systems GmbH
|
||||
|
@ -32241,6 +32272,7 @@
|
|||
74:DA:DA D-LinkIn D-Link International
|
||||
74:DA:EA TexasIns Texas Instruments
|
||||
74:DB:D1 Ebay Ebay Inc
|
||||
74:DD:CB ChinaLea China Leadshine Technology Co.,Ltd
|
||||
74:DE:2B LiteonTe Liteon Technology Corporation
|
||||
74:DF:BF LiteonTe Liteon Technology Corporation
|
||||
74:E0:6E Ergophon Ergophone GmbH
|
||||
|
@ -33377,6 +33409,7 @@
|
|||
80:96:B1 ARRISGro ARRIS Group, Inc.
|
||||
80:96:CA HonHaiPr Hon Hai Precision Ind. Co.,Ltd.
|
||||
80:97:1B Altenerg Altenergy Power System,Inc.
|
||||
80:97:33 Shenzhen Shenzhen Elebao Technology Co., Ltd
|
||||
80:9B:20 IntelCor Intel Corporate
|
||||
80:9F:9B SichuanA Sichuan AI-Link Technology Co., Ltd.
|
||||
80:9F:AB Fiberhom Fiberhome Telecommunication Technologies Co.,LTD
|
||||
|
@ -33844,6 +33877,7 @@
|
|||
84:EF:18 IntelCor Intel Corporate
|
||||
84:F1:29 Metrasca Metrascale Inc.
|
||||
84:F1:47 Cisco Cisco Systems, Inc
|
||||
84:F1:D0 EhoomeIo Ehoome Iot Private Limited
|
||||
84:F3:EB Espressi Espressif Inc.
|
||||
84:F4:93 OMSspols OMS spol. s.r.o.
|
||||
84:F6:4C CrossPoi Cross Point BV
|
||||
|
@ -34248,6 +34282,7 @@
|
|||
8C:14:7D:D0:00:00/28 Shenzhen Shenzhen Lanxus technology Co. Ltd.
|
||||
8C:14:7D:E0:00:00/28 Electric Electrical & Automation Larsen & Toubro Limited
|
||||
8C:14:B4 zte zte corporation
|
||||
8C:15:53 BeijingM Beijing Memblaze Technology Co Ltd
|
||||
8C:15:C7 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
8C:16:45 LCFCHeFe LCFC(HeFei) Electronics Technology co., ltd
|
||||
8C:17:B6 HuaweiDe Huawei Device Co., Ltd.
|
||||
|
@ -34398,6 +34433,7 @@
|
|||
8C:1F:64:47:A0:00/36 MissingL Missing Link Electronics, Inc.
|
||||
8C:1F:64:49:30:00/36 Security Security Products International, LLC
|
||||
8C:1F:64:49:80:00/36 YUYAMAMF YUYAMA MFG Co.,Ltd
|
||||
8C:1F:64:4A:C0:00/36 Vekto
|
||||
8C:1F:64:4B:00:00/36 U-Mei-Da U -Mei-Dah Int'L Enterprise Co.,Ltd.
|
||||
8C:1F:64:4B:B0:00/36 IWSGloba IWS Global Pty Ltd
|
||||
8C:1F:64:4C:10:00/36 Clock-O- Clock-O-Matic
|
||||
|
@ -34414,6 +34450,7 @@
|
|||
8C:1F:64:51:20:00/36 BlikSens Blik Sensing B.V.
|
||||
8C:1F:64:51:70:00/36 SmartRad Smart Radar System, Inc
|
||||
8C:1F:64:52:10:00/36 MP-SENSO MP-SENSOR GmbH
|
||||
8C:1F:64:52:50:00/36 UnitedSt United States Technologies Inc.
|
||||
8C:1F:64:53:40:00/36 SuryaEle Surya Electronics
|
||||
8C:1F:64:53:50:00/36 Columbus Columbus McKinnon
|
||||
8C:1F:64:53:60:00/36 BeijingL Beijing Lxtv Technology Co.,Ltd
|
||||
|
@ -34429,6 +34466,8 @@
|
|||
8C:1F:64:57:50:00/36 Yu-HengE Yu-Heng Electric Co., LTD
|
||||
8C:1F:64:57:A0:00/36 NPOECO-I NPO ECO-INTECH Ltd.
|
||||
8C:1F:64:57:B0:00/36 PotterEl Potter Electric Signal Company
|
||||
8C:1F:64:58:10:00/36 SpectraD SpectraDynamics, Inc.
|
||||
8C:1F:64:59:F0:00/36 DeltaCom Delta Computers LLC.
|
||||
8C:1F:64:5A:E0:00/36 SuzhouMo Suzhou Motorcomm Electronic Technology Co., Ltd
|
||||
8C:1F:64:5B:C0:00/36 Heitec Heitec Ag
|
||||
8C:1F:64:5D:30:00/36 EloyWate Eloy Water
|
||||
|
@ -34539,6 +34578,7 @@
|
|||
8C:1F:64:9C:30:00/36 CamozziA Camozzi Automation SpA
|
||||
8C:1F:64:9C:E0:00/36 ExiFlowM Exi Flow Measurement Ltd
|
||||
8C:1F:64:9C:F0:00/36 ASAPElec ASAP Electronics GmbH
|
||||
8C:1F:64:9D:40:00/36 Wolfspyr Wolfspyre Labs
|
||||
8C:1F:64:9D:80:00/36 Integerp Integer.pl S.A.
|
||||
8C:1F:64:9F:00:00/36 ePlant ePlant, Inc.
|
||||
8C:1F:64:9F:20:00/36 MBconnec MB connect line GmbH Fernwartungssysteme
|
||||
|
@ -34578,6 +34618,7 @@
|
|||
8C:1F:64:B5:60:00/36 Arcvideo
|
||||
8C:1F:64:B6:40:00/36 GSPSprac GSP Sprachtechnologie GmbH
|
||||
8C:1F:64:B7:70:00/36 Carestre Carestream Dental LLC
|
||||
8C:1F:64:B7:B0:00/36 Gateview Gateview Technologies
|
||||
8C:1F:64:B8:20:00/36 SeedCore Seed Core Co., LTD.
|
||||
8C:1F:64:B8:40:00/36 SPXFlowT SPX Flow Technology
|
||||
8C:1F:64:B8:D0:00/36 Tongyeln Tongye lnnovation Science and Technology (Shenzhen) Co.,Ltd
|
||||
|
@ -34684,6 +34725,7 @@
|
|||
8C:1F:64:FC:D0:00/36 elbit-EW elbit systems - EW and sigint - Elisra
|
||||
8C:1F:64:FD:10:00/36 Edgeware Edgeware AB
|
||||
8C:1F:64:FD:30:00/36 SmilicsT Smilics Technologies, S.L.
|
||||
8C:1F:64:FD:40:00/36 EmbsysSi Embsys Sistemas Embarcados
|
||||
8C:1F:64:FE:00:00/36 PotterEl Potter Electric Signal Company
|
||||
8C:1F:64:FE:30:00/36 PowerEle Power Electronics Espana, S.L.
|
||||
8C:1F:94 RFSurgic RF Surgical System Inc.
|
||||
|
@ -34739,6 +34781,7 @@
|
|||
8C:47:BE Dell Dell Inc.
|
||||
8C:49:62 Roku Roku, Inc
|
||||
8C:49:7A ExtremeN Extreme Networks, Inc.
|
||||
8C:49:B6 vivoMobi vivo Mobile Communication Co., Ltd.
|
||||
8C:4A:EE GigaTms Giga Tms Inc
|
||||
8C:4B:14 Espressi Espressif Inc.
|
||||
8C:4B:59 3DImagin 3D Imaging & Simulations Corp
|
||||
|
@ -35335,6 +35378,7 @@
|
|||
90:F6:44 HuaweiDe Huawei Device Co., Ltd.
|
||||
90:F6:52 Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
90:F7:2F Phillips Phillips Machine & Welding Co., Inc.
|
||||
90:F7:B2 NewH3CTe New H3C Technologies Co., Ltd
|
||||
90:F8:91 Kaonmedi Kaonmedia CO., LTD.
|
||||
90:F9:B7 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
90:FB:5B Avaya Avaya Inc
|
||||
|
@ -35977,6 +36021,7 @@
|
|||
98:A4:0E Snap Snap, Inc.
|
||||
98:A5:F9 Apple Apple, Inc.
|
||||
98:A7:B0 Mcst Mcst Zao
|
||||
98:A9:2D NewH3CTe New H3C Technologies Co., Ltd
|
||||
98:A9:42 Guangzho Guangzhou Tozed Kangwei Intelligent Technology Co., LTD
|
||||
98:AA:3C Willi-te Will i-tech Co., Ltd.
|
||||
98:AA:D7 BlueWave Blue Wave Networking Co Ltd
|
||||
|
@ -38690,6 +38735,7 @@ B8:7A:C9 Siemens Siemens Ltd.
|
|||
B8:7B:C5 Apple Apple, Inc.
|
||||
B8:7C:6F NXPChina NXP (China) Management Ltd.
|
||||
B8:7C:F2 ExtremeN Extreme Networks, Inc.
|
||||
B8:7E:E5 Intelbra Intelbras
|
||||
B8:80:35 Shenzhen Shenzhen Qihu Intelligent Technology Company Limited
|
||||
B8:80:4F TexasIns Texas Instruments
|
||||
B8:81:98 IntelCor Intel Corporate
|
||||
|
@ -41399,6 +41445,7 @@ D8:32:E3 XiaomiCo Xiaomi Communications Co Ltd
|
|||
D8:33:7F OfficeFA Office FA.com Co.,Ltd.
|
||||
D8:33:B7 Sagemcom Sagemcom Broadband SAS
|
||||
D8:34:EE StemAudi Stem Audio
|
||||
D8:36:5F Intelbra Intelbras
|
||||
D8:37:3B Shenzhen Shenzhen Jingxun Software Telecommunication Technology Co.,Ltd
|
||||
D8:37:BE Shenzhen Shenzhen Gongjin Electronics Co.,Lt
|
||||
D8:38:0D SHENZHEN SHENZHEN IP-COM Network Co.,Ltd
|
||||
|
@ -41655,6 +41702,7 @@ DA:1C:21 Sesam Sesam GmbH
|
|||
DA:28:EC HGGenuin HG Genuine
|
||||
DA:2B:DD AT&T AT&T, Inc.
|
||||
DA:41:62 Xperi Xperi Corporation
|
||||
DA:7D:2E DeltaCom Delta Computers LLC.
|
||||
DA:A1:19 Google Google, Inc.
|
||||
DA:C8:7D SEDevelo SE Development AB
|
||||
DA:FF:6B TeamPrec Team Precision Public Company Limited
|
||||
|
@ -41858,6 +41906,7 @@ DC:97:58 SichuanA Sichuan AI-Link Technology Co., Ltd.
|
|||
DC:98:40 Microsof Microsoft Corporation
|
||||
DC:99:14 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
DC:99:FE Armatura Armatura LLC
|
||||
DC:9A:7D HisenseV Hisense Visual Technology Co.,Ltd
|
||||
DC:9A:8E NanjingC Nanjing Cocomm electronics co., LTD
|
||||
DC:9B:1E Intercom Intercom, Inc.
|
||||
DC:9B:9C Apple Apple, Inc.
|
||||
|
@ -42803,6 +42852,7 @@ E8:80:2E Apple Apple, Inc.
|
|||
E8:80:D8 GNTEKEle GNTEK Electronics Co.,Ltd.
|
||||
E8:81:52 Apple Apple, Inc.
|
||||
E8:81:75 zte zte corporation
|
||||
E8:81:AB BeijingS Beijing Sankuai Online Technology Co.,Ltd
|
||||
E8:82:5B ARRISGro ARRIS Group, Inc.
|
||||
E8:84:A5 IntelCor Intel Corporate
|
||||
E8:84:C6 HuaweiTe Huawei Technologies Co.,Ltd
|
||||
|
@ -43075,6 +43125,7 @@ EC:5C:68 Chongqin Chongqing Fugui Electronics Co.,Ltd.
|
|||
EC:5C:69 Mitsubis Mitsubishi Heavy Industries Mechatronics Systems,Ltd.
|
||||
EC:5C:84 MurataMa Murata Manufacturing Co., Ltd.
|
||||
EC:5F:23 QinghaiK Qinghai Kimascend Electronics Technology Co. Ltd.
|
||||
EC:60:73 Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
EC:60:E0 Avi-OnLa Avi-On Labs
|
||||
EC:62:64 Global41 Global411 Internet Services, LLC
|
||||
EC:63:D7 IntelCor Intel Corporate
|
||||
|
@ -43767,6 +43818,7 @@ F4:6A:D7 Microsof Microsoft Corporation
|
|||
F4:6B:8C HonHaiPr Hon Hai Precision Ind. Co., Ltd.
|
||||
F4:6B:EF Sagemcom Sagemcom Broadband SAS
|
||||
F4:6D:04 ASUSTekC ASUSTek COMPUTER INC.
|
||||
F4:6D:2F Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
F4:6D:E2 zte zte corporation
|
||||
F4:6E:24 NECPerso NEC Personal Computers, Ltd.
|
||||
F4:6E:95 ExtremeN Extreme Networks, Inc.
|
||||
|
@ -43806,6 +43858,7 @@ F4:81:39 Canon Canon Inc.
|
|||
F4:83:CD Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
F4:83:E1 Shanghai Shanghai Clouder Semiconductor Co.,Ltd
|
||||
F4:84:4C TexasIns Texas Instruments
|
||||
F4:84:8D Tp-LinkT Tp-Link Technologies Co.,Ltd.
|
||||
F4:85:C6 FDTTechn FDT Technologies
|
||||
F4:87:71 Infoblox
|
||||
F4:87:C5 HuaweiDe Huawei Device Co., Ltd.
|
||||
|
|
|
@ -722,8 +722,9 @@
|
|||
<context>
|
||||
<name>ByteViewText</name>
|
||||
<message>
|
||||
<source>Allow hover selection</source>
|
||||
<translation>Hover-Auswahl erlauben</translation>
|
||||
<source>Allow hover highlighting</source>
|
||||
<oldsource>Allow hover selection</oldsource>
|
||||
<translation type="unfinished">Hover-Auswahl erlauben</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Show bytes as hexadecimal</source>
|
||||
|
@ -4322,6 +4323,14 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
<source>Decimal</source>
|
||||
<translation>Dezimal</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source><html><head/><body><p>Whether to do extra processing detecting the start of the ASCII representation at the end of a hex+ASCII line even if it looks like hex bytes.</p><p>Do not enable if the hex dump does not contain ASCII.</p></body></html></source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>ASCII identification:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Regular Expression</source>
|
||||
<translation>Regulärer Ausdruck</translation>
|
||||
|
@ -4386,6 +4395,26 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
<source>ExportPDU</source>
|
||||
<translation>ExportPDU</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>IP version:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP Version for to use for the dummy IP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Interface name:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The name of the interface to write to the import capture file</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Fake IF, Import from Hex Dump</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Maximum frame length:</source>
|
||||
<translation>Maximale Framelänge:</translation>
|
||||
|
@ -4412,7 +4441,7 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
</message>
|
||||
<message>
|
||||
<source><html><head/><body><p>The format in which to parse timestamps in the text file (e.g. %H:%M:%S.%f).</p><p>Format specifiers are based on strptime(3) with the addition of %f for second fractions. The precision of %f is determined from its length.</p></body></html></source>
|
||||
<translation type="unfinished"></translation>
|
||||
<translation><html><head/><body><p>Format des Zeitstempel der aus der Textdatei ausgelesen werden soll (z.B. %H:%M:%s.%f).</p><p>Formatzeichen basieren auf strptime(3) mit dem zusätzlichen Zeichen %f für Sekundenbruchteile. Die Länge von %f bestimmt die Präzision.</p></body></html></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>%H:%M:%S.%f</source>
|
||||
|
@ -4430,10 +4459,54 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
<source>Encapsulation type of the frames in the import capture file</source>
|
||||
<translation>Protokoll in das die Frames der zu importiernden Datei eingebettet sind</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet and IP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>IP</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and UDP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and TCP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and SCTP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and SCTP (DATA) header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Source address:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Destination address:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Dissector</source>
|
||||
<translation>Dissector</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP protocol ID for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP source address for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP destination address for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The UDP, TCP or SCTP source port for each frame</source>
|
||||
<translation>Der UDP, TCP oder SCTP Quellport für jeden Frame</translation>
|
||||
|
@ -4456,7 +4529,7 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and SCTP header</source>
|
||||
<translation>Jedem Frame einen Ethernet-, IPv4- und SCTP-Header voranstellen</translation>
|
||||
<translation type="vanished">Jedem Frame einen Ethernet-, IPv4- und SCTP-Header voranstellen</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>SCTP</source>
|
||||
|
@ -4484,7 +4557,7 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and UDP header</source>
|
||||
<translation>Jedem Frame einen Ethernet-, IPv4- und UDP-Header voranstellen</translation>
|
||||
<translation type="vanished">Jedem Frame einen Ethernet-, IPv4- und UDP-Header voranstellen</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>UDP</source>
|
||||
|
@ -4500,7 +4573,7 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and TCP header</source>
|
||||
<translation>Jedem Frame einen Ethernet-, IPv4- und TCP-Header voranstellen</translation>
|
||||
<translation type="vanished">Jedem Frame einen Ethernet-, IPv4- und TCP-Header voranstellen</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>TCP</source>
|
||||
|
@ -4520,11 +4593,11 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
</message>
|
||||
<message>
|
||||
<source>The IPv4 protocol ID for each frame</source>
|
||||
<translation>Die IPv4 Protokoll IP für jeden Frame</translation>
|
||||
<translation type="vanished">Die IPv4 Protokoll IP für jeden Frame</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and SCTP (DATA) header</source>
|
||||
<translation>Jedem Frame einen Ethernet-, IPv4- und SCTP-(Daten) Header voranstellen</translation>
|
||||
<translation type="vanished">Jedem Frame einen Ethernet-, IPv4- und SCTP-(Daten) Header voranstellen</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>SCTP (Data)</source>
|
||||
|
@ -4532,11 +4605,11 @@ Um zum Beispiel eine neue Datei zu jeder vollen Stunde zu haben, 1 Stunde angebe
|
|||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet and IPv4 header</source>
|
||||
<translation>Jedem Frame einen Ethernet- und IPv4-Header voranstellen</translation>
|
||||
<translation type="vanished">Jedem Frame einen Ethernet- und IPv4-Header voranstellen</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>IPv4</source>
|
||||
<translation>IPv4</translation>
|
||||
<translation type="vanished">IPv4</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The dissector to use for each frame</source>
|
||||
|
|
|
@ -722,7 +722,7 @@
|
|||
<context>
|
||||
<name>ByteViewText</name>
|
||||
<message>
|
||||
<source>Allow hover selection</source>
|
||||
<source>Allow hover highlighting</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
|
@ -4288,6 +4288,14 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
<source>Decimal</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source><html><head/><body><p>Whether to do extra processing detecting the start of the ASCII representation at the end of a hex+ASCII line even if it looks like hex bytes.</p><p>Do not enable if the hex dump does not contain ASCII.</p></body></html></source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>ASCII identification:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Regular Expression</source>
|
||||
<translation type="unfinished"></translation>
|
||||
|
@ -4352,6 +4360,26 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
<source>ExportPDU</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>IP version:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP Version for to use for the dummy IP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Interface name:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The name of the interface to write to the import capture file</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Fake IF, Import from Hex Dump</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Maximum frame length:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
|
@ -4396,10 +4424,54 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
<source>Encapsulation type of the frames in the import capture file</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet and IP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>IP</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and UDP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and TCP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and SCTP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IP and SCTP (DATA) header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Source address:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Destination address:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Dissector</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP protocol ID for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP source address for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IP destination address for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The UDP, TCP or SCTP source port for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
|
@ -4420,10 +4492,6 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
<source>Ethernet</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and SCTP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>SCTP</source>
|
||||
<translation type="unfinished"></translation>
|
||||
|
@ -4448,10 +4516,6 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
<source>Tag:</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and UDP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>UDP</source>
|
||||
<translation type="unfinished"></translation>
|
||||
|
@ -4464,10 +4528,6 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
<source>The Ethertype value of each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and TCP header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>TCP</source>
|
||||
<translation type="unfinished"></translation>
|
||||
|
@ -4484,26 +4544,10 @@ For example, use 1 hour to have a new file created every hour on the hour.</sour
|
|||
<source>Ethertype (hex):</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The IPv4 protocol ID for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet, IPv4 and SCTP (DATA) header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>SCTP (Data)</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Prefix each frame with an Ethernet and IPv4 header</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>IPv4</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>The dissector to use for each frame</source>
|
||||
<translation type="unfinished"></translation>
|
||||
|
|
|
@ -722,8 +722,9 @@
|
|||
<context>
|
||||
<name>ByteViewText</name>
|
||||
<message>
|
||||
<source>Allow hover selection</source>
|
||||
<translation>Permitir selección al desplazar</translation>
|
||||
<source>Allow hover highlighting</source>
|
||||
<oldsource>Allow hover selection</oldsource>
|
||||
<translation type="unfinished">Permitir selección al desplazar</translation>
|
||||
</message>
|
||||
<message>
|
||||
<source>Show bytes as hexadecimal</source>
|
||||
|
@ -4283,6 +4284,14 @@ Por ejemplo, use 1 hora para tener creado un nuevo archivo cada hora en punto.</
|
|||
<source>Decimal</source>
|
||||
<translation>Decimal</translation>
|
||||