osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

these two guys are actually range-strings and not value-string 

so it is surprising we didnt catche these before.


gcc complains about strict alignment on these



svn path=/trunk/; revision=31842
This commit is contained in:
Ronnie Sahlberg 2010-02-09 07:42:38 +00:00
parent 96bcad4ea8
commit 7d52b73e5d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
epan/dissectors/packet-isakmp.c
View File

@ -4215,11 +4215,11 @@ proto_register_isakmp(void)
"ISAKMP Transform ID", HFILL }},
{ &hf_isakmp_id_type_v1,
{ "ID type", "isakmp.id.type",
FT_UINT8, BASE_DEC, VALS(&vs_v1_id_type), 0x0,
FT_UINT8, BASE_DEC, RVALS(&vs_v1_id_type), 0x0,
"ISAKMP (v1) ID Type", HFILL }},
{ &hf_isakmp_id_type_v2,
{ "ID type", "isakmp.id.type",
FT_UINT8, BASE_DEC, VALS(&vs_v2_id_type), 0x0,
FT_UINT8, BASE_DEC, RVALS(&vs_v2_id_type), 0x0,
"ISAKMP (v2) ID Type", HFILL }},
{ &hf_isakmp_protoid,
{ "Protocol ID", "isakmp.protoid",
@ -4430,7 +4430,7 @@ proto_register_isakmp(void)
"The domain to be authenticated in", HFILL }},
{ &hf_isakmp_cfg_attr_xauth_status,
{ "XAUTH STATUS", "isakmp.cfg.attr.xauth.status",
FT_UINT16, BASE_DEC, VALS(&cfgattr_xauth_status), 0x00,
FT_UINT16, BASE_DEC, VALS(cfgattr_xauth_status), 0x00,
"A variable that is used to denote authentication success or failure", HFILL }},
{ &hf_isakmp_cfg_attr_xauth_next_pin,
{ "XAUTH TYPE", "isakmp.cfg.attr.xauth.next_pin",