Hi Keval,

based on your screenshot you seem to have a proprietary encapsulation in
the UDP payload (we can see the string nr-rrc and a BCCH-BCH message - that
contains a MIB - is 3 bytes long only). So presumably here the real data
you want to decode is 0x06f2d4?
You should request to whoever defined this encapsulation the corresponding
Wiresahrk dissector / plugin that calls the NR-RRC dissector. Or use
another encapsulation method as the one described by Anders.

For the payload 06f2d4, the decoding is:
NR Radio Resource Control (RRC) protocol
    BCCH-BCH-Message
        message: mib (0)
            mib
                systemFrameNumber: 0c [bit length 6, 2 LSB pad bits, 0000
11.. decimal value 3]
                subCarrierSpacingCommon: scs15or60 (0)
                ssb-SubcarrierOffset: 15
                dmrs-TypeA-Position: pos2 (0)
                pdcch-ConfigSIB1
                    controlResourceSetZero: 5
                    searchSpaceZero: 10
                cellBarred: notBarred (1)
                intraFreqReselection: allowed (0)
                spare: 00 [bit length 1, 7 LSB pad bits, 0... .... decimal
value 0]

Best regards,
Pascal.


Le ven. 25 oct. 2019 à 04:24, Keval Malde <kevalma...@5g.iith.ac.in> a
écrit :

> 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> wrote:
>
>> On Oct 24, 2019, at 11:29 AM, Keval Malde <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>
>> 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
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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

Reply via email to