Pascal Quantin's profile - activity

Hi, this is the expected PDU content when the UE as a valid security context available. See 3GPP 24.501 for details.

Please let time to reviewers to go though your changes: they are all volunteers doing this on their spare time and somet

Hi, done in this merge request.

Hi Norbie, the warning message fragment payload is invalid for a SIB8 with a single fragment, thus the error generated.

Well for me this is clearly a non compliance with 3GPP specifications that should be addressed.

Could you clarify why your system put a BCCH DL-SCH message for the SIB1? This does not seem to match the SIB1 definitio

So does the SIB1 container contains a SIB1 message and not a BCCH-DL-SCH message, as suggested by 3GPP 38.473? Could you

So does the SIB1 container contains a SIB1 message and not a BCCH-DL-SCH message, as uggested by 3GPP 38.473? Could you

Hi, deciphering is not supported due to copyright reasons.

Hi, Wireshark currently does not support decoding the RRC container in the UE context modification request message, so

That's correct, you should use the 3.5.0 development builds as a release upgrade is not a bugfix and thus is not candida

That's correct, you should use the 3.5.0 development builds as a release upgrade is not a bugfix and thus is not candida

That's correct, you should use the 3.5.0 development builds found here: https://www.wireshark.org/download/automated/

That's correct, you should use the 3.5.0 development builds found here: https://www.wireshark.org/download/automated/

That's correct, you should use the the 3.5.0 development builds found here: https://www.wireshark.org/download/automated

Hi, If it is decoded as a RRC connection reestablishment it means that you payload is not a RRC connection setup. Pleas

NAS-5GS dissector is now compliant with v16.6.0 starting from Wireshark v3.5.0rc0-194-gd75fef88fb.

I intend to upgrade the dissector soon, I'm simply lacking the spare time and energy to upgrade it. It will come soon.

Capture from stdin in Windows is currently broken and will be fixed in 3.4.1. The fix is under review here.

Capture from stdin in Windows is currently borken and will be fixed in 3.4.1. The fix is under review here.

Hi, 1/ please clarify your current output and what you would like to have 2/ FT_BOOLEAN should use TFS(), not VALS().

Hi, move the wireshark-win64-libs-3.2 folder outside of your build tree and update your WIRESHARK_LIB_DIR accordingly,

Right now there is no named dissector registered for the HandoverCommand PDU. You need to have it encapsulated in a a S1

Well, nowhere in your question it was clear that you had a pcap that would match this proprietary log. If you expect to

Hi, tshark cannot read this proprietary log format, so you are out of luck. Best regards, Pascal.

Hi Dan, better report this and ask for help on the Npcap bug tracker: https://github.com/nmap/nmap/issues Best regards

You can use the Analyze -> Decode As to add extra TCP ports for HTTP2 decoding.

Thiss is now implemented in https://code.wireshark.org/review/#/c/36084/

Create an enhancement bug on bugs.wireshark.org and attach the pcap

The F1AP dissector should already handle UL CCCH messages. For DCCH messages, what you have is NR PDCP PDUs and not RRC

The F1AP dissector should already handle DL and UL CCCH messages. For DCCH messages, what you have is NR PDCP PDUs and n

The F1AP dissector should already handled DL and UL CCCH messages. For DCCH messages, what you have is NR PDCP PDUs and

And calling NR RRC dissector is now implemented in Wireshark v3.3.0rc0-479-g4ef8ace610

Hi, 1/ the code is ready to call the NR-RRC disssector but the lookup_rrc_dissector_handle() was never finished. I'm go