[Anders Broman <anders.broman@xxxxxxxxxxxx>]

Hi

A preference would work. If I remember correctly we got bug reports on malformed packets possibly because of test tools filling the container with junk

Or the container can contain different encodings(?).

Regards

Anders

 

From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Pascal Quantin
Sent: den 21 juni 2013 06:10
To: damker; Community support list for Wireshark
Subject: Re: [Wireshark-users] about decode RRC message in the RRC-Container at the RANAP protocol

 

Hi,

actually the code to do it is already present but was deactivated with the following comment: "Don't dissect RRC container, it seems to only cause grief". We would need Ander's feedback to know why he deactivated this code.

You can activate it by changing the glbl_dissect_container variable in epan/dissectors/packet-ranap.c from FALSE to TRUE.

Anders, maybe we could put this as a preference? Or was it triggering bugs?

 

Best regards,

Pascal.

 

 

2013/6/21 damker <damker@xxxxxxxx>

could wireshark provide the convenience of decoding RRC message in the RRC-Container at the RANAP protocol

attachment is a sample packet of RANAP contains RRC-Container.

 

---

damker

 

 

 

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