aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjmayer <jmayer@f5534014-38df-0310-8fa8-9805f1628bb7>2009-07-08 15:29:37 +0000
committerjmayer <jmayer@f5534014-38df-0310-8fa8-9805f1628bb7>2009-07-08 15:29:37 +0000
commit8479a5ab61269cfcd012fd18154e2a5dc9b48158 (patch)
treeb78d75c5a58589d3a71fe3bc062fee359c33ae2a
parentb9b6ddda4aa4f8fb1234ad5021500728551e29d7 (diff)
Currently, the expert code notifies if a packet is addressed
to 224.0.0.x with a TTL>1. Some protocols (notably VRRP and GLBP) send out a TTL of 255 and thus cause a notice. That should be fixed, so for now: Add a FIXME about that. git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@29024 f5534014-38df-0310-8fa8-9805f1628bb7
-rw-r--r--epan/dissectors/packet-ip.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/epan/dissectors/packet-ip.c b/epan/dissectors/packet-ip.c
index 0ebfe0a739..edfd8cae6a 100644
--- a/epan/dissectors/packet-ip.c
+++ b/epan/dissectors/packet-ip.c
@@ -1611,6 +1611,13 @@ dissect_ip(tvbuff_t *tvb, packet_info *pinfo, proto_tree *parent_tree)
*
* Flag a low TTL if the packet is not destined for a multicast address
* (e.g. 224.0.0.0/4).
+ *
+ * FIXME: Add an exception list, as Some protocols seem to insist on
+ * doing differently:
+ * - IETF's VRRP (rfc3768) always uses 224.0.0.18 with 255
+ * - Cisco's GLPB always uses 224.0.0.102 with 255
+ * Even more, VRRP and GLBP should probably be flagged as an error, if
+ * seen with any TTL except 255.
*/
if (is_a_local_network_control_block_addr(dst32)) {
if (iph->ip_ttl != 1) {