Hi, So the decoding should be:
0000 00 0c 00 18 6e 72 2d 72 72 63 2e 62 63 63 68 2e nr-rrc.mib 6e 72 2d 72 72 63 2e 6d 69 62 0010 62 63 68 00 00 00 00 00 00 00 00 00 00 00 00 00 (nr-rrc.bcch.bch 6e 72 2d 72 72 63 2e 62 63 63 68 2e 62 63 68) 0020 6e 72 2d 72 72 63 00 00 00 05 00 01 06 f2 d4 Regards Anders From: Pascal Quantin <pascal.quan...@gmail.com> Sent: den 25 oktober 2019 09:39 To: Community support list for Wireshark <wireshark-users@wireshark.org> Cc: Anders Broman <anders.bro...@ericsson.com> Subject: Re: [Wireshark-users] 5G NR-RRC dissector issue Hi, A UE is receiving a BCCH-BCH message that encapsulates a MIB. Are 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 <wireshark-users@wireshark.org <mailto:wireshark-users@wireshark.org> > a écrit : 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.pcapng The code change can be followed here <https://code.wireshark.org/review/#/c/34852/> https://code.wireshark.org/review/#/c/34852/ Dissection result: Regards Anders From: Wireshark-users <wireshark-users-boun...@wireshark.org <mailto:wireshark-users-boun...@wireshark.org> > On Behalf Of Keval Malde Sent: den 25 oktober 2019 04:24 To: Community support list for Wireshark <wireshark-users@wireshark.org <mailto:wireshark-users@wireshark.org> > Subject: Re: [Wireshark-users] 5G NR-RRC dissector issue No In wireshark there is no such seperate NR RRC over UDP option. But then if not UDP then how am I supposed to send and receive packet ? On Fri, 25 Oct, 2019, 2:05 AM Guy Harris, <g...@alum.mit.edu <mailto:g...@alum.mit.edu> > wrote: On Oct 24, 2019, at 11:29 AM, Keval Malde <kevalma...@5g.iith.ac.in <mailto:kevalma...@5g.iith.ac.in> > wrote: > I am trying to dissect 5G NR RRC MIB paket but it is not working, any > possible help would be appreciated. Please find the attachment below. What is the payload of that UDP packet supposed to be? Is there some "NR RRC over UDP protocol" being used? ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org <mailto:wireshark-users@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org <mailto:wireshark-users-requ...@wireshark.org> ?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org <mailto:wireshark-users@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org <mailto:wireshark-users-requ...@wireshark.org> ?subject=unsubscribe
smime.p7s
Description: S/MIME cryptographic signature
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe