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

[Jaap Keuter <jaap.keuter@xxxxxxxxx>]

Hi,

This all points to things related to the actual traffic in the capture. As Pascal says, without a capture file itself this is virtually impossible to address. 

For the first issue you could file a complete filled out report at https://gitlab.com/wireshark/wireshark/-/issues

Regards,

Jaap

 

On 28 Oct 2021, at 16:59, Chilla Sunil Kumar-Trainee <cskumar@xxxxxxxxxxxxxxxxxxxx> wrote:

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
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
3. 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

 

___________________________________________________________________________
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