úÎ!3:2D   SafeƒpingCould not create the socketpingYUnable to send when the event manager indicated that the socket was ready for writes. pingbUnable to send the entirity on an ICMP request. The field is the number of bytes actually sent.ping[Unable to receive when the event manager indicated that the socket was ready for reads. pingCould not close the socket.None.Ú Safe%NoneFX_afFping%Ping a range of hosts simultaneously.pingìPing a set of hosts simultaneously. Performs one ping for each host and reports the elapsed nanoseconds for the response. If a key is missing from the resulting map, it indicates that a response was not received from that host.ping!Microseconds to wait for responsepingRangeping(Elapsed nanoseconds for responding hostsping!Microseconds to wait for responsepingHostsping(Elapsed nanoseconds for responding hostsNoneFX_af.õpingÿ.Ping a group of hosts simultaneously. Performs a configurable number of pings for each host and reports the elapsed nanoseconds for each response. If the array of durations is smaller than the total number of pings, it indicates that some ICMP requests for that host were lost or corrupted.ÿÍThe function also accepts an cutoff for unresponsive hosts. If a host does not respond to the initial number of pings equal to the cutoff, this function does not attempt further pings to the host. Consider the case in which this function performs 20 pings per host with a 5e6 microsecond timeout. Without the unresponsive cutoff, a single nonresponsive host would cause this function to always run for 100 seconds. However, with the cutoff set to 3, this function would stop trying pinging the host after there was no response to any of the first 3 pings. However if there were a response to any of the first 3 pings, then all 20 pings would continue to be sent. This does not necessarily guarantee that this function would run for less than 100 seconds. A host might respond to the initial ping and then go offline. Or a host might take just under 5 seconds to respond to each ping. However, both of these situations are uncommon. What is much more common is that someone includes a bad IP address in the list of hosts, and a low cutoff can considerably reduce the amount of time wasted on such pings. To prevent the cutoff behavior, set it to the number of pings per host. pingDSend multiple pings to each host in a range of hosts simultaneously.ping!Microseconds to wait for responseping-Microsecond delay between pings to same host pingNumber of pings per host pingNonresponsive cutoffpingHosts ping!Microseconds to wait for responseping-Microsecond delay between pings to same host pingNumber of pings per host pingNonresponsive cutoffpingRangeping(Elapsed nanoseconds for responsive hosts NoneFX_f1­ ping:Ping an IPv4 address. Blocks until a response is received. ping!Microseconds to wait for responsepingHostpingElapsed nanoseconds None1è        #ping-0.1.0.3-5ysvLJs7iQKAd0sfqhPedpNetwork.Icmp.PingNetwork.Icmp.CommonNetwork.Icmp.MarshalNetwork.Icmp.Ping.DebugNetwork.Icmp.Ping.HostsNetwork.Icmp.Ping.MultihostsNetwork.Icmp.Ping.Single IcmpExceptionIcmpExceptionSocketIcmpExceptionSendIcmpExceptionSendBytesIcmpExceptionReceiveIcmpExceptionCloserangehosts multihosts multirangehostsizeOfIcmpHeaderpokeIcmpHeaderpeekIcmpHeaderTypepeekIcmpHeaderSequenceNumberpeekIcmpHeaderPayloaddebug