Thanks, It worked after setting "Dissect T-PDU as None" GTP preference. Though in previous versions it worked with default settings.
Regards Ranjeet S On Fri, Dec 25, 2020 at 2:56 PM Pascal Quantin <pas...@wireshark.org> wrote: > > Hi, > > Le ven. 25 déc. 2020 à 06:02, Ranjeet kumar singh <ranjeet...@gmail.com> a > écrit : >> >> it is present in 3.25 and missing in 3.4.2. >> >> Please see attached images. in one this field is present and in other >> it's missing. >> >> I have not made any setting changes. Just installed released wireshark >> and opened a captured file with gtp packet. > > > I cannot reproduce your issue: by setting the "Dissect T-PDU as None" GTP > preference, I do get the T-PDU data payload displayed with 3.4.2. If I let > the default value (TPDU Heuristic) it properly identifies the payload as IP. > So it could be related to your GTP-U PDU where the heuristic fails for > example. Please check the behavior if you sendure to set the preference to > None and share the packet if it still fails. > > Best regards. > >> >> >> Regards >> Ranjeet S >> >> On Thu, Dec 24, 2020 at 1:46 PM Dario Lombardo <lom...@gmail.com> wrote: >> > >> > Can you please tell a version in which is present and a version in which >> > is not? >> > >> > On Thu, Dec 24, 2020 at 8:54 AM Ranjeet kumar singh <ranjeet...@gmail.com> >> > wrote: >> >> >> >> Hi >> >> >> >> Gtp packets used to have a tpdu_data field. >> >> >> >> I don't see it in the latest wireshark. >> >> >> >> This is causing my lua plugins to break. >> >> >> >> Can someone please fix it. >> >> >> >> Regards >> >> Ranjeet S >> >> ___________________________________________________________________________ >> >> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> >> Archives: https://www.wireshark.org/lists/wireshark-dev >> >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> >> >> >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe >> > >> > >> > >> > -- >> > >> > Naima is online. >> > >> > ___________________________________________________________________________ >> > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> > Archives: https://www.wireshark.org/lists/wireshark-dev >> > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> Archives: https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
