On Sun, Mar 17, 2013 at 05:06:00PM +1100, Michael Chesterton wrote: > * What led up to the situation? > network testing > * What exactly did you do (or not do) that was effective (or > ineffective)? > sudo ping -l 20 some lan connected address > * What was the outcome of this action? > sent 4 or 5 pings asap, then returned to one ping per second (-i) > * What outcome did you expect instead? > I expected it to send 20 pings asap > > weirdly and interestingly, > > sudo strace -o /tmp/ping.out ping -l 20 some lan connected address > > works as I expected, with it preloading 20 pings. also > > sudo ping -l 20 localhost > > works as I expected, with it preloading 20 pings.
Confirmed that this bug is still present in newer versions. If behavior is correct when running under strace, that suggests a timing related issue. I'd guess that what's happening is that if ping receives and processes a response before it has finished sending the preload packets then the preload routine is interrupted and it immediately falls back to standard behavior. But I haven't investigated. On the other hand, I don't see ping sending more than 12 preload packets at all, under strace or not. Tried against nearby hosts and remote hosts on the other end of VPN tunnels (thus with larger RTTs). noah
signature.asc
Description: PGP signature
