Guy Harris wrote:
...
> What you can do is to have *three* fields, all with the name "mtp3.sls",
> with one having the right layout for the ITU style, one having the right
> layout for the 5-bit ANSI style, and one having the right layout for the
> 8-bit ANSI style. (Is this yet another case of "us Yanks vs. the rest
> of the world"? Sigh....)
Yup. Only ours is better. ;-)
(There are also lots of other national variants, though...)
> In "proto_register_x25()", for example, we have entries such as
>
> { &hf_x25_p_s_mod8,
> { "P(S)", "x.25.p_s", FT_UINT8, BASE_HEX, NULL, 0x0E,
> "Packet Send Sequence Number", HFILL }},
> { &hf_x25_p_s_mod128,
> { "P(S)", "x.25.p_s", FT_UINT8, BASE_HEX, NULL, 0xFE,
> "Packet Send Sequence Number", HFILL }},
>
> and the X.25 dissector puts the field into the protocol tree using
> "hf_x25_p_s_mod8" if it's a mod-8 connection and "hf_x25_p_s_mod128" if
> it's a mod-128 connection.
>
> You can filter on, say, "x.25.p_s == 3", and it'll correctly match
> packets with a P(S) field with a value of 3, regardless of whether the
> packet came from a mod-8 connection or a mod-128 connection.
Sweet! I'll re-code it...begin:vcard
n:Morriss;Jeff
tel;fax:+1-856-222-9947
tel;work:+1-856-787-2824
x-mozilla-html:FALSE
url:http://www.ulticom.com
org:Ulticom, Inc.;Customer Support
version:2.1
email;internet:jeff.morriss@xxxxxxxxxxx
title:Product Support Engineer
adr;quoted-printable:;;Ulticom, Inc.=0D=0A1020 Briggs Rd.=0D=0A;Mount Laurel;NJ;08054;USA
fn:Jeff Morriss
end:vcard
