Thomas Guyot-Sionnest wrote: >> Here is a tcpdump of check_mk pinging... >> >> 11:29:24.042801 IP 10.0.0.4 > adsl-79.dacor.net: ICMP echo request, id >> 58673, seq 0, length 64 >> 11:29:24.043603 IP adsl-79.dacor.net > 10.0.0.4: ICMP echo reply, id 58673, >> seq 0, length 64 >> 11:29:24.043768 IP 10.0.0.4 > adsl-79.dacor.net: ICMP echo request, id >> 58673, seq 0, length 64 >> 11:29:24.124046 IP 10.0.0.4 > adsl-79.dacor.net: ICMP echo request, id >> 58673, seq 0, length 64 >> 11:29:24.204417 IP 10.0.0.4 > adsl-79.dacor.net: ICMP echo request, id >> 58673, seq 0, length 64 >> 11:29:24.284728 IP 10.0.0.4 > adsl-79.dacor.net: ICMP echo request, id >> 58673, seq 0, length 64 > > The problem with check_mk pinging is that the ICMP sequence number > doesn't increase. Some devices treat this as a duplicate packed and > ignore it (I'm not sure what the RFC specify but this is probably the > correct behaviour). > > Just use the non-mk host check command for the host definition with the > check_mk command for services and you should be fine.
I wondered about that and searched but could find no info either way about how the seq was supposed to work. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
