Issues are tracked over on Gitlab. https://gitlab.com/wireshark/wireshark/-/issues
Could you move your pcap and notes to a new issue over there? On Mon, Jun 26, 2023 at 10:33 AM S. Jäkel via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > Hi Wireshark team, > > an RDM packet from E1.37-1 with the name > FREQUENCY_MODULATION_DESCRIPTION is interpreted and displayed > incorrectly by wireshark. > There was forgotten to consider an int32 which stands before the actual > description in the package. > In the attached record you can see the problem in the 2nd package > Enclosed a screenshot with explanation and also the RDM protocol 1.37-1 > > It would be nice if this bug is fixed. > > With kind regards > > S. Jäkel > > > WireSharkVersion > > Version 4.0.6 (v4.0.6-0-gac2f5a01286a). > > Compiled (64-bit) using Microsoft Visual Studio 2022 (VC++ 14.32, build > 31332), > with GLib 2.72.3, with PCRE2, with zlib 1.2.12, with Qt 5.15.2, with > libpcap, > with Lua 5.2.4, with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt > 1.10.1, with > Kerberos (MIT), with MaxMind, with nghttp2 1.46.0, with brotli, with > LZ4, with > Zstandard, with Snappy, with libxml2 2.9.14, with libsmi 0.4.8, with > QtMultimedia, with automatic updates using WinSparkle 0.5.7, with > AirPcap, with > SpeexDSP (using bundled resampler), with Minizip, with binary plugins. > > Running on 64-bit Windows 10 (22H2), build 19045, with Intel(R) Core(TM) > i7-4930K CPU @ 3.40GHz (with SSE4.2), with 16319 MB of physical memory, > with > GLib 2.72.3, with PCRE2 10.40 2022-04-14, with Qt 5.15.2, with Npcap > version > 1.71, based on libpcap version 1.10.2-PRE-GIT, with c-ares 1.18.1, with > GnuTLS > 3.6.3, with Gcrypt 1.10.1, with nghttp2 1.46.0, with brotli 1.0.9, with LZ4 > 1.9.3, with Zstandard 1.5.2, without AirPcap, with light display mode, > without > HiDPI, with LC_TYPE=German_Germany.utf8, binary plugins supported. > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
