Wireshark-dev: Re: [Wireshark-dev] What ftypes are "compatible" enough for duplicate fields?
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Hadriel Kaplan <hadriel.kaplan@xxxxxxxxxx>
Date: Fri, 21 Feb 2014 13:43:48 -0500
On Feb 21, 2014, at 1:29 PM, Evan Huus <eapache@xxxxxxxxx> wrote:

> That patch almost (but not quite) matches what's listed in
> README.dissector (lines 1018-1024). I believe the README is correct,
> in which case the patch is simply out of date (I believe it's missing
> FT_AX25 and FT_VINES, and possibly others I haven't done a thorough
> check).

Heh, you told me to go read that before and I forgot to check it.

So this then:
- FT_INT8, FT_INT16, FT_INT24 and FT_INT32
- FT_UINT8, FT_UINT16, FT_UINT24, FT_UINT32, FT_IPXNET and FT_FRAMENUM
- FT_UINT64 and FT_EUI64
- FT_STRING, FT_STRINGZ and FT_UINT_STRING
- FT_FLOAT and FT_DOUBLE
- FT_BYTES, FT_UINT_BYTES, FT_AX25, FT_ETHER, FT_VINES, FT_OID and FT_REL_OID
- FT_ABSOLUTE_TIME and FT_RELATIVE_TIME

-hadriel