Instructions for reporting bugs can be found on the wiki: https://wiki.wireshark.org/ReportingBugs
On 17 March 2017 at 16:36, Sabyasachi Samal <[email protected]> wrote: > Hi Anders, > Thanks for the response. I am using the message structure of TS 36.413 > v13.3.0 and wireshark development version Version 2.3.0-2658-gfe285c6 > (v2.3.0rc0-2658-gfe285c6). I do not know the process of filling a ticket > for wireshark. Attaching the trace here so that you guys can help.[image: > Inline image 1] > > On Thu, Mar 16, 2017 at 2:49 PM, Anders Broman <[email protected] > > wrote: > >> Hi, >> >> The S1AP dissector in trunk is based on TS 36.413 V13.5.0 (2016-12) so I >> guess it should decode the message. >> >> The best is to raise a bug attaching a trace with the RerouteNASRequest >> message and describe what is not dissected correctly. >> >> Regards >> >> Anders >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Sabyasachi Samal >> *Sent:* den 16 mars 2017 10:11 >> *To:* Community support list for Wireshark <[email protected] >> > >> *Subject:* [Wireshark-users] R13 S1AP message "Reroute NAS Request" is >> not decoding completely using 2.3.0 >> >> >> >> Hi, >> >> R13 baseline S1AP message "RerouteNASRequest" is not decoding completely >> using 2.3.0. Can anyone suggest how to proceed on this or is there any plan >> supporting this. >> >> >> >> >> -- Graham Bloice
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
