Wireshark-bugs: [Wireshark-bugs] [Bug 7474] New: Parse and properly display LTE RADIUS AVP 3GPP-
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7474
Summary: Parse and properly display LTE RADIUS AVP
3GPP-User-Location-Info
Product: Wireshark
Version: 1.8.0
Platform: x86
OS/Version: Windows 7
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: phikus@xxxxxxxxx
Created attachment 8767
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8767
LTE RADIUS dump
Build Information:
Version 1.8.0 (SVN Rev 43431 from /trunk-1.8)
Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> 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.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Jun 21 2012), with AirPcap.
Running on 32-bit Windows 7, build 7600, with WinPcap version 4.0.2 (packet.dll
version 4.0.0.1040), based on libpcap version 0.9.5, GnuTLS 2.12.18, Gcrypt
1.4.6, without AirPcap.
Built using Microsoft Visual C++ 10.0 build 40219
--
Hello.
According to 3GPP specification (3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Interworking between the Public Land Mobile Network (PLMN)
supporting packet based services and
Packet Data Networks (PDN)
(Release 9))
3GPP-User-Location-Info has the following description:
22 - 3GPP-User-Location-Info
Bits
Octets 8 7 6 5 4 3 2 1
1 3GPP type = 22
2 3GPP Length= m
3 Geographic Location Type
4-m Geographic Location (octet string)
3GPP Type: 22
Length=m, where m depends on the Geographic Location Type
For example, m= 10 in the CGI and SAI types.
Geographic Location Type field is used to convey what type of location
information is present in the 'Geographic Location' field. For GGSN, the
Geographic Location Type values and coding are as defined in 3GPP TS 29.060
[24]. For P-GW, the Geographic Location Type values and coding are defined as
follows:
0 CGI
1 SAI
2 RAI
3-127 Spare for future use
128 TAI
129 ECGI
130 TAI and ECGI
131-255 Spare for future use
Geographic Location field is used to convey the actual geographic information
as indicated in the Geographic Location Type. For GGSN, the coding of this
field is as specified in 3GPP TS 29.060 [24]. For P-GW, the coding of this
field shall be as follows:
- If the Geographic Location Type has a value indicating CGI, SAI, RAI, TAI
or ECGI (i.e. the value field is equal to 0, 1, 2, 128, or 129), the coding of
the Geographic Location field shall be as per clauses 8.21.1 to 8.21.5,
respectively, in 3GPP TS 29.274 [81],
- If the Geographic Location Type has a value indicating TAI and ECGI (i.e.
the value field is equal to 130), in Geographic Location field both TAI and
ECGI shall be encoded one after another as per clauses 8.21.4 and 8.21.5 in
3GPP TS 29.274 [81]. TAI information shall be encoded first starting with Octet
4 of 3GPP-User-Location-Info.
Geographic Location Type and Geographic Location fields are Octet String type.
But in the Wireshark I just see it like this (dump attached):
AVP: l=21 t=Vendor-Specific(26) v=3GPP(10415)
VSA: l=15 t=3GPP-User-Location-Info(22): 8252f02009c552f01103d09102
[Length: 15]
Geographic Location Type: 130
Is there any way to parse and display this field including all sub-values
(SAI/RA/etc)?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
