[smokeping-users] FPing alternative

[Israel Brewster]

Sorry about resurrecting an old dead thread, but I was wondering if  
there had been any changes in the last few months since the last  
posting, perhaps updates to the fping probe or the like? This  
continues to be an issue for us, and I am not at all happy with the  
work around I have in place (sending 4 pings with a 15 second interval).

To rehash: the problem we are running into is that when using fping  
against certain devices, only one or two packets are returned,  
regardless of device function and number of packets sent. Setting a  
higher packet interval (such at the 15 seconds mentioned previously)  
allows a limited number of additional packets to return, but is not a  
workable solution. From previous discussions, it would appear that the  
issue is with fping not updating the sequence number, but patching  
that issue is beyond my skill level. Thanks!

-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
-----------------------------------------------


On May 19, 2008, at 8:10 AM, Israel Brewster wrote:

>
>
>
> On May 17, 2008, at 11:03 AM, Niko Tyni wrote:
>
>> On Sat, May 17, 2008 at 02:20:04PM -0400, Mike Lerley wrote:
>>
>>> Fair enough; however, I have turned on and off all options I can
>>> find on the
>>> router related to that sort of thing and nothing changes.  More
>>> importantly,
>>> I can do this:
>>>
>>> root at george:~# ping -f tobeys.gotdns.com
>>> PING tobeys.gotdns.com (24.39.29.68) 56(84) bytes of data.
>>> .......................................
>>> --- tobeys.gotdns.com ping statistics ---
>>> 3609 packets transmitted, 3570 received, 1% packet loss, time  
>>> 47185ms
>>> rtt min/avg/max/mdev = 23.229/31.162/72.274/7.039 ms, pipe 6, ipg/
>>> ewma
>>> 13.078/27.893 ms
>>>
>>> Clearly, there is no packet rate limiting in effect here...
>>
>> It's most probably looking at the ICMP sequence number.  While the
>> 'regular ping' increments the sequence number for each ping, fping
>> apparently uses is as an index to the hosts it's pinging. So the  
>> first
>> host gets sequence number 0 for all pings, the second one gets 1 etc.
>>
>> The device probably considers the unchanging sequence number an  
>> attack
>> and stops responding.
>>
>> It should be quite easy to patch fping to store the information in  
>> the
>> payload instead and increase the sequence number like the rest of the
>> world does. No, no patch at least yet :)
>>
>> Cheers,
>
> Now that is the best answer I have heard yet- it actually makes sense
> (to a degree, at least), and fits the observed facts. Any chance of
> such a patch being written by someone? I'd be happy to test it, if
> so... Actually, I'd almost be happy to write it, except I don't think
> my understanding of networks, ping payloads, and how this all works is
> quite up to the task :).
>
> -----------------------------------------------
> Israel Brewster
> Computer Support Technician
> Frontier Flying Service Inc.
> 5245 Airport Industrial Rd
> Fairbanks, AK 99709
> (907) 450-7250 x293
> -----------------------------------------------
>>
>> -- 
>> Niko
>>
>> _______________________________________________
>> smokeping-users mailing list
>> smokeping-users at lists.oetiker.ch
>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users