https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10702

David Perry <boolean...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |boolean...@gmail.com

--- Comment #1 from David Perry <boolean...@gmail.com> ---
Looking at the attached trace in a modern Wireshark, it looks like this may
have been addressed.

Filtering on `eth.dst`, stream #1 now shows "CIP Format ID: IEC 61883-4:
MPEG2-TS data transmission (0x20)" and has a "Video Data" member instead of the
"Audio Data" member of stream #0. Stream #2 shows as having "AVBTP Subtype:
Vendor Specific Format STream (0x6f)" followed by data.

Build information of my test:
3.3.0 (v3.3.0rc0-1214-gda8c28dc67ac)

Compiled (64-bit) with Qt 5.9.5, with libpcap, with POSIX capabilities (Linux),
without libnl, with GLib 2.56.4, with zlib 1.2.11, with SMI 0.4.8, with c-ares
1.14.0, with Lua 5.2.4, with GnuTLS 3.5.18 and PKCS #11 support, with Gcrypt
1.8.1, with MIT Kerberos, without MaxMind DB resolver, with nghttp2 1.30.0,
with
brotli, with LZ4, with Zstandard, with Snappy, with libxml2 2.9.4, with
QtMultimedia, without automatic updates, with SpeexDSP (using system library).

Running on Linux 5.3.0-51-generic, with Intel(R) Core(TM) i5-2500K CPU @
3.30GHz
(with SSE4.2), with 15907 MB of physical memory, with locale
LC_CTYPE=en_CA.UTF-8, LC_NUMERIC=en_CA.UTF-8, LC_TIME=en_CA.UTF-8,
LC_COLLATE=C,
LC_MONETARY=en_CA.UTF-8, LC_MESSAGES=en_CA.UTF-8, LC_PAPER=en_CA.UTF-8,
LC_NAME=en_CA.UTF-8, LC_ADDRESS=en_CA.UTF-8, LC_TELEPHONE=en_CA.UTF-8,
LC_MEASUREMENT=en_CA.UTF-8, LC_IDENTIFICATION=en_CA.UTF-8, with light display
mode, without HiDPI, with libpcap version 1.8.1, with GnuTLS 3.5.18, with
Gcrypt
1.8.1, with brotli 1.0.4, with zlib 1.2.11, binary plugins supported (18
loaded).

Built using gcc 7.5.0.

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to