I don't really know. When I ran "ping 10.10.0.1" it just worked. fping -p250 didn't. On Nov 30, 2017 4:38 PM, "Toke Høiland-Jørgensen" wrote: > Georgios Amanakis writes: > > > To correct myself, fping did not die prematurely, it was getting no > > responses from the remote host because its p parameter was too short at > > default for an RTT of 600ms. After looking at the source, I realized that > > it is affected but the s parameter of flent, and changed that instead. > > Ah, gotcha. That makes sense. So fping will ignore replies that arrive > after it sent the next packet? That's kinda odd... Does regular ping > behave the same way? > > -Toke >