Wireshark · Wireshark-dev: Re: [Wireshark-dev] Not possible to set UAT values unsigned 32

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

Wireshark-dev: Re: [Wireshark-dev] Not possible to set UAT values unsigned 32

From: Guy Harris <guy@xxxxxxxxxxxx>

Date: Mon, 20 Aug 2018 11:34:30 -0700

On Aug 20, 2018, at 8:36 AM, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote:

> In GTP
> UAT_FLD_HEX(uat_pdcp_keys_records, teid, "TEID", "Tunnel Endpoint Identifier"),
>  
> Does not allow to use the full 32 bits TEID, I think uat.[ch] needs to use strtoll (64bits) and to the size check accordingly.

Or use ws_hexstrtou32(), which does the checking for you.

References:
- [Wireshark-dev] Not possible to set UAT values unsigned 32
  - From: Anders Broman

Prev by Date: [Wireshark-dev] Not possible to set UAT values unsigned 32
Next by Date: [Wireshark-dev] I am seeing a bunch of 'Dissector bug reports after I scanned my captures with tshark
Previous by thread: [Wireshark-dev] Not possible to set UAT values unsigned 32
Next by thread: [Wireshark-dev] I am seeing a bunch of 'Dissector bug reports after I scanned my captures with tshark
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube