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

Fix interpretation of BSO field in Type III headers. 

Use a correct right value_string table.

Change-Id: I75ca54dc040b123a460d67fc1b6d49d9e062a49e
Reviewed-on: https://code.wireshark.org/review/34651
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2019-09-29 16:24:04 -07:00
parent 3367cbab17
commit 486c6fd07c
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
epan/dissectors/packet-cisco-erspan.c
View File

@ -99,6 +99,15 @@ static const value_string erspan_encap_vals[] = {
{0, NULL}
};
static const value_string erspan_bso_vals[] = {
{0, "Good or unknown integrity"},
{1, "Short frame"},
{2, "Oversized frame"},
{3, "CRC or alignment error"},
{0, NULL},
};
static const value_string erspan_truncated_vals[] = {
{0, "Not truncated"},
{1, "Truncated"},
@ -380,7 +389,7 @@ proto_register_erspan(void)
0x1800, NULL, HFILL }},
{ &hf_erspan_bso,
{ "Bad/Short/Oversized", "erspan.bso", FT_UINT16, BASE_DEC, VALS(erspan_truncated_vals),
{ "Bad/Short/Oversized", "erspan.bso", FT_UINT16, BASE_DEC, VALS(erspan_bso_vals),
0x1800, NULL, HFILL }},