It is akin to looking at Where is Waldo pictures for 1 ms. Overall MHO is that pings are pretty much worthless. At that point the PC sending the ping would be dependent on it's internal timeout.
Set max ping console casual code#
If Server has code that intercepts ICMP traffic, and puts it into a queue of responses to send later, the response time, theoretically, could be anything. The response time depends on transit times between each hop, assuming all links are active, all routers accept / forward ICMP, and Server accepts and responds to the ICMP. Packets: Sent = 2, Received = 0, Lost = 2 (100% loss), C:\Users\FredFlintstone>ping -w 10000 -n 2 The default for Windows might be 4 seconds, but it can be longer. If you meant some other " ping" (for example delay between some application-specific request/response), it will probably differ completely. One thing to note - I'm talking here about ICMP only. So, I think it's safe to assume this to be the practical limit. Ping responses longer than that are equivalent to no responses at all. With iputils implementation of ping it seems to be 10 seconds - not sure about it, as it's not stated in the man page, but the code says something like this: #define MAXWAIT 10 /* max seconds to wait for response */ The specific value depends on implementation: Practically though, there's a threshold value after which lack of reply will be treated as no reply at all ( timeout). From a quick glance at RFC 1122 I don't see any formal constraints here. Theoretically, the time between echo request and reply can be long.
0 kommentar(er)
