The BoostPinger is more picky about received packets, because when running in
authorGuilherme Maciel Ferreira <guilherme.maciel.ferreira@intra2net.com>
Mon, 2 May 2011 10:30:42 +0000 (12:30 +0200)
committerGuilherme Maciel Ferreira <guilherme.maciel.ferreira@intra2net.com>
Mon, 2 May 2011 10:30:42 +0000 (12:30 +0200)
commitf6ec93865b209a8c4d30f4ca01bd26cce369e676
tree55b74a209b37ac543e926f5b35167073c057174b
parent4cf6fed48601cab98d23381c63418d6d872a131d
The BoostPinger is more picky about received packets, because when running in
parallel with other BoostPingers, it could receive echo replies from any host,
leading to things like:
    26 bytes from 209.85.149.104: icmp_seq=1 ttl=54 time=24 ms   <-- pinger A received packet from host A
    26 bytes from 209.85.149.104: icmp_seq=1 ttl=54 time=1999 ms <-- pinger B received packet from host A??
     - Host up: www.postbank.de                                  <-- what? You didn't receive any packet from the host you had ping
     - Stick to the original ping interval: 10s
     - Time elapsed since last ping: 12s                         <-- OK, pinger A parsed the packet from host A
     - Stick to the original ping interval: 5s
     - Time elapsed since last ping: 6s                          <-- WRONG, pinger B should not parse the packet from host A
src/host/boostpinger.cpp
src/icmp/icmppacket.cpp
src/icmp/icmppacket.h