Re: [Wireshark-users] Where is wireshark config file?

-Original Message- From: Wireshark-users On Behalf Of Peng Yu Sent: den 2 mars 2021 07:18 To: Community support list for Wireshark Subject: Re: [Wireshark-users] Where is wireshark config file? Hi Graham, >> When I run tshark, I see something like this. This pem file was >> loaded on

Re: [Wireshark-users] NR-RRC Dissector

Hi, If you followed the tread you could see that Pascal wrote(see below) an explanation why the solution I tried was wrong so I reverted that code and the sample does not work as you can see. This might work: text2pcap.exe -l 252 MIB.txt" mib.pcapng" With the following content of the .txt

Re: [Wireshark-users] NR-RRC Dissector

Hi, Did you check the replies to your previous mails? https://www.wireshark.org/lists/wireshark-users/201910/msg00019.html Regards Anders From: Wireshark-users On Behalf Of Manoj Kumar Sent: den 29 oktober 2019 13:0

Re: [Wireshark-users] 5G NR-RRC dissector issue

and PDCP over UDP and it worked. Is there any method to decode RRC message over UDP as I want to test 5G NR RRC other messages also. Thanks for the help On Fri, Oct 25, 2019 at 1:05 PM Anders Broman via Wireshark-users mailto:wireshark-users@wireshark.org> > wrote: Hi, The NR-RRC mes

Re: [Wireshark-users] 5G NR-RRC dissector issue

you sure we need to expose the MIB dissector directly? Best regards, Pascal. Le ven. 25 oct. 2019 à 09:34, Anders Broman via Wireshark-users mailto:wireshark-users@wireshark.org> > a écrit : Hi, The NR-RRC messages has to be dissected by calling dissector by name. Currently “M

Re: [Wireshark-users] 5G NR-RRC dissector issue

Hi, The NR-RRC messages has to be dissected by calling dissector by name. Currently “MIB” is not handled but I have amended the code to expose it. Instead of building a UDP packet with the MIB Octets as data you can create an “Exported PDU” by using text2pcap text2pcap.exe -l 252 MIB.txt mib.p