https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5475
Summary: gsm_a_dtap: incorrect "Extraneous Data" when decoding Packet Flow Identifier Product: Wireshark Version: 1.4.2 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Low Component: Wireshark AssignedTo: wireshark-bugs@wireshark.org ReportedBy: rs...@arcor.de Build Information: wireshark 1.4.2 Copyright 1998-2010 Gerald Combs <ger...@wireshark.org> and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled (32-bit) with GTK+ 2.20.1, with GLib 2.24.1, with libpcap 1.1.1, with libz 1.2.3, without POSIX capabilities, without libpcre, without SMI, without c-ares, without ADNS, with Lua 5.1, without Python, with GnuTLS 2.8.6, with Gcrypt 1.4.4, without Kerberos, without GeoIP, without PortAudio, without AirPcap. Running on Linux 2.6.34.7-0.5-default, with libpcap version 1.1.1, with libz 1.2.3, GnuTLS 2.8.6, Gcrypt 1.4.4. Built using gcc 4.5.0 20100604 [gcc-4_5-branch revision 160292]. -- Due to a change applied to packet-gsm_a_gm.c:de_sm_pflow_id() after Wireshark version 1.2.x an Activate PDP Context Accept message which contains a Packet Flow Identifier IE is now incorrectly marked as containing "Extraneous Data" since current_offset is no longer incremented accordingly. Using echo 000000 8a 42 03 0b 23 91 1f 93 96 8e e8 74 07 01 01 04 2b 06 01 21 0a 00 00 03 27 14 80 80 21 10 03 00 00 10 81 06 0a 00 00 01 83 06 0a 00 00 02 34 01 01 | text2pcap -l 147 /dev/stdin extrdata.pcap and Decode User DLT 0 as gsm_a_dtap Wireshark 1.4.2 displays ... Packet Flow Identifier Element ID: 52 Length: 1 0... .... = Spare bit(s): 0 .000 0001 = Packet Flow Identifier (PFI): Signaling (1) Extraneous Data while Wireshark 1.2.8 displays ... Packet Flow Identifier Element ID: 52 Length: 1 Packet Flow Identifier: (1) Signaling -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ___________________________________________________________________________ Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe