Dez Cadena wrote: >I had some non-responsive fping targets in my config so I tried both >ping and fping from the command line. >Same target, same options (5 packets, 64bytes size, 1sec between packets): >fping produced 100% packet loss (as expected) >ping produced 0% packet loss (!) > > I have absolutely the same problem over one of our links.
fping 192.168.101.1 -b 1500 192.168.101.1 is unreachable ping 192.168.200.230 -s 1500 PING 192.168.200.230 (192.168.200.230) 1500(1528) bytes of data. 1508 bytes from 192.168.200.230: icmp_seq=1 ttl=254 time=24.9 ms but fping 192.168.200.230 -b 12 192.168.200.230 is alive I looked into packets and see that there is difference in content. This is 2Mbit hdlc link betwee cisco 3660 and 1751... Strange but true... >AFAIK, both fping and ping send ICMP echo requests so how come the same >target is responsive through >ping and non-responsive through fping? Any ideas? The target is a cisco >26xx router. > > -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/smokeping-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
