aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2017-11-20 10:06:28 -0800
committerGuy Harris <guy@alum.mit.edu>2017-11-20 18:07:23 +0000
commitfdc3023bece20993237f8e5ae959f23fff437d69 (patch)
tree827acdbaf062a94d0f740f46f499b0419436c43d
parent6917ec769e4d23fe2fa212bec69c9ce9b65c1671 (diff)
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 <guy@alum.mit.edu>
-rw-r--r--epan/dissectors/packet-rx.c3
1 files changed, 2 insertions, 1 deletions
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 */