bbtest-net ping results red for host that is alive

[Asif Iqbal]

why is bbtest-net fails but regular ping or fping finds it alive for
this host? This behavior is consistent

(hobbit)@hobbit:~/server$ ./bin/bbcmd bbtest-net --no-update --ping
--checkresponse ----debug > out
2009-06-09 13:01:10 Using default environment file
/export/home/hobbit/server/etc/hobbitserver.cfg

(hobbit)@hobbit:~/server$ grep 1.2.3.4 out
2009-06-09 13:02:04 Adding to combo msg: status 1,2,3,4.conn red <!--
[flags:ordAsTLe] --> Tue Jun  9 13:01:10 2009 conn NOT ok
      status 1,2,3,4.conn red <!-- [flags:ordAsTLe] --> Tue Jun  9
13:01:10 2009 conn NOT ok
&red 1.2.3.4 is unreachable
status 1,2,3,4.conn red <!-- [flags:ordAsTLe] --> Tue Jun  9 13:01:10
2009 conn NOT ok
Service conn on 1.2.3.4 is not OK : Host does not respond to ping
&red 1.2.3.4 is unreachable

(hobbit)@hobbit:~/server$ fping 1.2.3.4
1.2.3.4 is alive
(hobbit)@hobbit:~/server$ ping 1.2.3.4
1.2.3.4 is alive

(hobbit)@hobbit:~/server$ grep 216.111.66.254 etc/bb-hosts
1.2.3.4     1.2.3.4 # testip badconn:10:20:30

(hobbit)@hobbit:~/server$ grep 216.111.66.254 tmp/hobbitd.chk
@@HOBBITDCHK-V1||1.2.3.4|conn|1.1.1.1|red|ordAsTLe|red|1244566684|1244560884|1244568484|0|0|136967|1244647284|status
1,2,3,4.conn red <!-- [flags:ordAsTLe] --> Tue Jun  9 12:56:51 2009
conn NOT ok \n\nService conn on 1.2.3.4 is not OK : Host does not
respond to ping\n\n\nSystem unreachable for 238 poll periods (70836
seconds)\n\n&red 1.2.3.4 is unreachable\nTraceroute
results:\ntraceroute to 1.2.3.4 (1.2.3.4), 15 hops max, 40 byte
packets\n 1 [..stripped to save to the innocents..]\n 8  * *\n 9  *
*\n10  * *\n11  * *\n12  * *\n13  * *\n14  * *\n\n\n\n\n||
(hobbit)@hobbit:~/server$

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?