Wireshark · Wireshark-dev: Re: [Wireshark-dev] Issue with the NR-RRC Di-sector

[Pascal Quantin <pascal@xxxxxxxxxxxxx>]

Hi,

Le jeu. 28 oct. 2021 à 17:45, Chilla Sunil Kumar-Trainee <cskumar@xxxxxxxxxxxxxxxxxxxx> a écrit :

Hi,

I had an issue with RRC messages.

1. In F1Setup Request message , it is not Showing the complete message information. SIB1 Information is missing and showing that  [Expert Info (Warning/Undecoded): something unknown here [too long integer(per_normally_small_nonnegative_whole_number)]]
   [something unknown here [too long integer(per_normally_small_nonnegative_whole_number)]]
   [Severity level: Warning]
   [Group: Undecoded]. Please find this in the attached snapshot – F1 setup issue.png

We cannot provide any support with a screenshot only. It could be that your SIB1 message is not properly encoded of a bug in Wireshark.

2. I am not able to see some RRC messages like NAS Security mode Command Complete and AS Security mode Command. Please find the attached snapshot - RRC.png

If you use ciphering, this is expected as Wirehark does not include the (potentially patented) code to perform deciphering (that would be UE specific also due to the different ciphering key).

2. Not able to find the message transmission in between gNB_DU and UE (Over the Air messages) - Please find this in the attached snapshot –need rrc.png

See the response above.

 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe