Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 7474] Parse and properly display LTE RADIUS AVP 3GPP-User-

Date: Tue, 22 Oct 2013 01:34:32 +0000

changed bug 7474

What Removed Added
Status RESOLVED UNCONFIRMED
CC   [email protected]
Resolution FIXED ---
Ever confirmed 1  

Comment # 7 on bug 7474 from
I am trying to extract 3GPP_User_Location_Info from Radius messages. However in
this instance it is not extracting info correctly 
$ tshark -v TShark 1.10.2 (SVN Rev 51934 from /trunk-1.10)
tshark -T fields -e radius.Calling_Station_Id -e radius.3GPP_User_Location_Info
-e radius.3GPP_IMEISV -e radius.Framed-IP-Address -E header=y -E separator=, -E
quote=d -r Nikola_TEST_cap.pcap | head
radius.Calling_Station_Id,radius.3GPP_User_Location_Info,radius.3GPP_IMEISV,radius.Framed-IP-Address
"6149891xxxx",,"3598220413753808","144.131.70.63"
"6145563xxxx",,"3598220423540908","101.175.33.128"
For some reason the 3GPP-User-Location-Id AVP doesn’t get extracted by tshark,
although Wireshark shows/decodes the AVP just file.
I upgraded my copy of Wireshark on the Mac to the latest but still seeing the
same issue. The AVP is listed in the dictionary and in tshark –G fields so
suspect it may be a bug? Other 3GPP fields are extracted ok.

we are running a later version 1.10.2 and the 3GPP-User-Location-Info field is
not displaying at all in tshark


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