Hello, When I check GTPv2 message with expanding subtree, it is found that TEID is decoded as decimal as below. TEID/GRE Key: 34604084
Fully Qualified Tunnel Endpoint Identifier (F-TEID) : S11 MME GTP-C interface, TEID/GRE Key: 0x02100434, IPv4 10.64.194.1
asked 31 Aug '13, 00:41  Kaz edited 31 Aug '13, 07:44  cmaynard ♦♦ |
One Answer:
is there anyone who knows reason of this? Yes. That's how Anders Broman coded it when he committed the change in r35378. answered 31 Aug '13, 07:52 cmaynard ♦♦ showing 5 of 11 show 6 more comments |
Thanks for the comment! Do you know any intention? I also re-checked other pcap files and as long as I check GTP version 1 and S1AP seem to decode as Hex as below.
S1AP
gTP-TEID: 052c2201
GTP version1
TEID: 0x22000db5
So for me, unifying to hex looks beautiful rather than mix hex and decimal. But there might be some purpose for the future use. Do you know any reason?
Well, it'd probably be better if the representation was consistent, but whether it should be displayed as hexadecimal, decimal, or both may be subjective. What does the GTPv2 specification say about how this field should be represented?
In any case, feel free to open a bug report asking for the value to be consistently displayed.
In 3GPP TS 36.444, it seems saying TEID type is octets string. But overall there seems no clear definition...
I also think it is not right or wrong answer to display as whether hexadecimal or decimal in the current situation.
Well, let's see if bug report would help to get conclusion about this question. :)
Since it's an octet string, I think the right thing to do is to display it in hexadecimal. I committed a change in r51789 to do that and scheduled the change to the roadmap for 1.10.2 and 1.8.102.
Sorry, for late response. Thanks a lot for help!
Hi, Have been a wireshark + GTP user for quite some time now. Just realized that teid displayed value is in decimal for gtpv2.teid however hex for gtpv2.f_teid_gre_key.
This is again inconvenient while trying to analyse /observe GTP flows. Can we please make the gtpv2.teid as HEX.
5345 { &hf_gtpv2_t, 5346 {"TEID flag (T)", "gtpv2.t", 5347 FT_UINT8, BASE_DEC, NULL, 0x08, 5348 "If TEID field is present or not", HFILL} 5349 }, 5350 { &hf_gtpv2_message_type,
Wireshark development releases already dump the gtpv2.teid as HEX and DEC. You just need to upgrade to a nightly build as found here: https://www.wireshark.org/download/automated/
Hi, Was this issue ever solved? I have WS 1.12.7 and still see GTPv2 pkts TEID and SQN in decimal but not Hexa.
Thanks a lot
Br, Bulphi
This change is part of the upcoming Wireshark 2.0. In the meantime you can already download the 1.99.9 development preview from Wireshark download page.
From the comment of @cmaynard from Sept 5, 2013(!) I would expect it to be in the 1.12 branch already. And backported to 1.10. and 1.8 as per comment on r51789. Did this make it into the git repo?
This was done for the gtpv2.f_teid_gre_key field, not for the gtpv2.teid field. This one is changed in 2.0 branch.