Wireshark-bugs: [Wireshark-bugs] [Bug 10688] New: Extended 3GPP-GPRS-Negotiated-QoS-profile stri
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 10 Nov 2014 18:02:22 +0000
Bug ID 10688
Summary Extended 3GPP-GPRS-Negotiated-QoS-profile strings decoded incompletely
Product Wireshark
Version 1.12.1
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter dandreye@cisco.com 

Created attachment 13250 [details]
Traces & Screenshots

Build Information:
C:\Program Files\Wireshark>wireshark -v

C:\Program Files\Wireshark>

wireshark 1.12.2rc0-32-gce0e169 (v1.12.2rc0-32-gce0e169 from master-1.12)

Copyright 1998-2014 Gerald Combs <gerald@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 (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 26 2014),
with

AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, with 7851MB of physical memory.


Built using Microsoft Visual C++ 10.0 build 40219

C:\Program Files\Wireshark>
--
"Extended"R99 UMTS GTP QoS profile string
"99-0b921f9196fefe7429ffff00fa00fa00" that we use to request QCI9 with
MBR=256Mbps up/down has only the former "fa00" out of "fa00fa00" decoded as
shown in the screenshot attached. The issue is seen in RADIUS Acct messages
(e.g. Start in packet #1 in the trace attached) and in Diameter CCR-i messages
on Gy interface (e.g. packet #4 in the same trace). 

As per applicable 3GPP specs (in particular 24.008) "extended" string is used
to overcome the 8640kbps limit of the "standard" string and so be able to
request up to 256Mbps. The string can be extended even further by another 4
octets to request up to 512Mbps.

You are receiving this mail because:
  • You are watching all bug changes.