Hi Anthony,

I do not have a computer to open your pcap right now but in the screenshot you 
shared the NAS message seems to be ciphered, which would explain why Wireshark 
cannot decode it.

Best regards,
Pascal.

15 févr. 2025 17:47:37 Tancredi, Anthony via Wireshark-users 
<wireshark-users@wireshark.org>:

> Wireshark Support,
>  
> 
> Is this a known issue that the LPP message Reset Positioning Information can 
> not be decoded by the Wireshark Dissector. All other LPP messages can be 
> decoded properly. When logging the LPP message in another tool such as 
> Qualcomm QXDM, the message can be decoded successfully.
>  
> 
> Fram 5720:
>  
> 
> [Image]
>  
> 
>  
> 
> Version 4.2.4-01 (Git commit c966d79150b6).
>  
> 
> Compiled (64-bit) using Microsoft Visual Studio 2019 (VC++ 14.29, build 
> 30151),
> with GLib 2.78.0, with Qt 6.5.3, with libpcap, with zlib 1.3.0, with PCRE2, 
> with
> Lua 5.2.4 (with UfW patches), with GnuTLS 3.8.3 and PKCS #11 support, with
> Gcrypt 1.10.2-unknown, with Kerberos (MIT), with MaxMind, with nghttp2 1.57.0,
> with nghttp3 1.0.0, with brotli, with LZ4, with Zstandard, with Snappy, with
> libxml2 2.11.5, with libsmi 0.5.0, with QtMultimedia, with automatic updates
> using WinSparkle 0.8.0, with AirPcap, with Minizip, with binary plugins.
>  
> 
> Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) Core(TM)
> i7-4790S CPU @ 3.20GHz (with SSE4.2), with 6143 MB of physical memory, with 
> GLib
> 2.78.0, with Qt 6.5.3, with Npcap version 1.78, based on libpcap version 
> 1.10.4,
> with PCRE2 10.42 2022-12-11, with c-ares 1.27.0, with GnuTLS 3.8.3, with 
> Gcrypt
> 1.10.2-unknown, with nghttp2 1.57.0, with nghttp3 1.0.0, with brotli 1.0.9, 
> with
> LZ4 1.9.3, with Zstandard 1.5.2, without AirPcap, with light display mode, 
> with
> HiDPI, with QPA plugin "windows", with LC_TYPE=English_United States.utf8,
> binary plugins supported.
>  
> 
> Thanks,
> Anthony
_______________________________________________
Wireshark-users mailing list -- wireshark-users@wireshark.org
To unsubscribe send an email to wireshark-users-le...@wireshark.org

Reply via email to