From fdc3023bece20993237f8e5ae959f23fff437d69 Mon Sep 17 00:00:00 2001 From: Guy Harris Date: Mon, 20 Nov 2017 10:06:28 -0800 Subject: OpenAFS always puts out 3 bytes of padding in an ack packet. Change-Id: Ia956ac7df43c307a8d5adac5c78c894017f7f7ec Reviewed-on: https://code.wireshark.org/review/24513 Reviewed-by: Guy Harris --- epan/dissectors/packet-rx.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/epan/dissectors/packet-rx.c b/epan/dissectors/packet-rx.c index 34533307bf..48b77646de 100644 --- a/epan/dissectors/packet-rx.c +++ b/epan/dissectors/packet-rx.c @@ -374,7 +374,8 @@ dissect_rx_acks(tvbuff_t *tvb, packet_info *pinfo, proto_tree *parent_tree, int * * RX as a protocol seems to be completely undefined and seems to lack * any sort of documentation other than "read the source of any of the - * (compatible?) implementations. + * (compatible?) implementations. The OpenAFS source indicates that + * 3 bytes of padding are written after the acks. */ if (tvb_reported_length_remaining(tvb, offset)>3) { offset += 3; /* guess. some implementations add 3 bytes */ -- cgit v1.2.3