{ "mode": "man", "parameter": "ping6", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/ping6/8/json", "generated": "2026-05-30T07:08:25Z", "synopsis": "ping [-aAbBdDfhLnOqrRUvV46] [-c count] [-F flowlabel] [-i interval] [-I interface]\n[-l preload] [-m mark] [-M pmtudiscoption] [-N nodeinfooption] [-w deadline]\n[-W timeout] [-p pattern] [-Q tos] [-s packetsize] [-S sndbuf] [-t ttl]\n[-T timestamp option] [hop...] {destination}", "sections": { "NAME": { "content": "ping - send ICMP ECHOREQUEST to network hosts\n", "subsections": [] }, "SYNOPSIS": { "content": "ping [-aAbBdDfhLnOqrRUvV46] [-c count] [-F flowlabel] [-i interval] [-I interface]\n[-l preload] [-m mark] [-M pmtudiscoption] [-N nodeinfooption] [-w deadline]\n[-W timeout] [-p pattern] [-Q tos] [-s packetsize] [-S sndbuf] [-t ttl]\n[-T timestamp option] [hop...] {destination}\n", "subsections": [] }, "DESCRIPTION": { "content": "ping uses the ICMP protocol's mandatory ECHOREQUEST datagram to elicit an ICMP ECHORESPONSE\nfrom a host or gateway. ECHOREQUEST datagrams (“pings”) have an IP and ICMP header, followed\nby a struct timeval and then an arbitrary number of “pad” bytes used to fill out the packet.\n\nping works with both IPv4 and IPv6. Using only one of them explicitly can be enforced by\nspecifying -4 or -6.\n\nping can also send IPv6 Node Information Queries (RFC4620). Intermediate hops may not be\nallowed, because IPv6 source routing was deprecated (RFC5095).\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-4", "content": "Use IPv4 only.\n", "flag": "-4" }, { "name": "-6", "content": "Use IPv6 only.\n", "flag": "-6" }, { "name": "-a", "content": "Audible ping.\n", "flag": "-a" }, { "name": "-A", "content": "Adaptive ping. Interpacket interval adapts to round-trip time, so that effectively not\nmore than one (or more, if preload is set) unanswered probe is present in the network.\nMinimal interval is 200msec unless super-user. On networks with low RTT this mode is\nessentially equivalent to flood mode.\n", "flag": "-A" }, { "name": "-b", "content": "Allow pinging a broadcast address.\n", "flag": "-b" }, { "name": "-B", "content": "Do not allow ping to change source address of probes. The address is bound to one\nselected when ping starts.\n", "flag": "-B" }, { "name": "-c", "content": "Stop after sending count ECHOREQUEST packets. With deadline option, ping waits for count\nECHOREPLY packets, until the timeout expires.\n", "flag": "-c" }, { "name": "-d", "content": "Set the SODEBUG option on the socket being used. Essentially, this socket option is not\nused by Linux kernel.\n", "flag": "-d" }, { "name": "-D", "content": "Print timestamp (unix time + microseconds as in gettimeofday) before each line.\n", "flag": "-D" }, { "name": "-f", "content": "Flood ping. For every ECHOREQUEST sent a period “.” is printed, while for every\nECHOREPLY received a backspace is printed. This provides a rapid display of how many\npackets are being dropped. If interval is not given, it sets interval to zero and outputs\npackets as fast as they come back or one hundred times per second, whichever is more.\nOnly the super-user may use this option with zero interval.\n", "flag": "-f" }, { "name": "-F", "content": "IPv6 only. Allocate and set 20 bit flow label (in hex) on echo request packets. If value\nis zero, kernel allocates random flow label.\n", "flag": "-F" }, { "name": "-h", "content": "Show help.\n", "flag": "-h" }, { "name": "-i", "content": "Wait interval seconds between sending each packet. Real number allowed with dot as a\ndecimal separator (regardless locale setup). The default is to wait for one second\nbetween each packet normally, or not to wait in flood mode. Only super-user may set\ninterval to values less than 2 ms.\n", "flag": "-i" }, { "name": "-I", "content": "interface is either an address, an interface name or a VRF name. If interface is an\naddress, it sets source address to specified interface address. If interface is an\ninterface name, it sets source interface to specified interface. If interface is a VRF\nname, each packet is routed using the corresponding routing table; in this case, the -I\noption can be repeated to specify a source address. NOTE: For IPv6, when doing ping to a\nlink-local scope address, link specification (by the '%'-notation in destination, or by\nthis option) can be used but it is no longer required.\n", "flag": "-I" }, { "name": "-l", "content": "If preload is specified, ping sends that many packets not waiting for reply. Only the\nsuper-user may select preload more than 3.\n", "flag": "-l" }, { "name": "-L", "content": "Suppress loopback of multicast packets. This flag only applies if the ping destination is\na multicast address.\n", "flag": "-L" }, { "name": "-m", "content": "use mark to tag the packets going out. This is useful for variety of reasons within the\nkernel such as using policy routing to select specific outbound processing.\n", "flag": "-m" }, { "name": "-M", "content": "Select Path MTU Discovery strategy. pmtudiscoption may be either do (prohibit\nfragmentation, even local one), want (do PMTU discovery, fragment locally when packet\nsize is large), or dont (do not set DF flag).\n", "flag": "-M" }, { "name": "-N", "content": "IPv6 only. Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.\nCAPNETRAW capability is required.\n\nhelp\nShow help for NI support.\n\nname\nQueries for Node Names.\n\nipv6\nQueries for IPv6 Addresses. There are several IPv6 specific flags.\n\nipv6-global\nRequest IPv6 global-scope addresses.\n\nipv6-sitelocal\nRequest IPv6 site-local addresses.\n\nipv6-linklocal\nRequest IPv6 link-local addresses.\n\nipv6-all\nRequest IPv6 addresses on other interfaces.\n\nipv4\nQueries for IPv4 Addresses. There is one IPv4 specific flag.\n\nipv4-all\nRequest IPv4 addresses on other interfaces.\n\nsubject-ipv6=ipv6addr\nIPv6 subject address.\n\nsubject-ipv4=ipv4addr\nIPv4 subject address.\n\nsubject-name=nodename\nSubject name. If it contains more than one dot, fully-qualified domain name is\nassumed.\n\nsubject-fqdn=nodename\nSubject name. Fully-qualified domain name is always assumed.\n", "flag": "-N" }, { "name": "-n", "content": "Numeric output only. No attempt will be made to lookup symbolic names for host addresses.\n", "flag": "-n" }, { "name": "-O", "content": "Report outstanding ICMP ECHO reply before sending next packet. This is useful together\nwith the timestamp -D to log output to a diagnostic file and search for missing answers.\n", "flag": "-O" }, { "name": "-p", "content": "You may specify up to 16 “pad” bytes to fill out the packet you send. This is useful for\ndiagnosing data-dependent problems in a network. For example, -p ff will cause the sent\npacket to be filled with all ones.\n", "flag": "-p" }, { "name": "-q", "content": "Quiet output. Nothing is displayed except the summary lines at startup time and when\nfinished.\n", "flag": "-q" }, { "name": "-Q", "content": "Set Quality of Service -related bits in ICMP datagrams. tos can be decimal (ping only)\nor hex number.\n\nIn RFC2474, these fields are interpreted as 8-bit Differentiated Services (DS),\nconsisting of: bits 0-1 (2 lowest bits) of separate data, and bits 2-7 (highest 6 bits)\nof Differentiated Services Codepoint (DSCP). In RFC2481 and RFC3168, bits 0-1 are used\nfor ECN.\n\nHistorically (RFC1349, obsoleted by RFC2474), these were interpreted as: bit 0 (lowest\nbit) for reserved (currently being redefined as congestion control), 1-4 for Type of\nService and bits 5-7 (highest bits) for Precedence.\n", "flag": "-Q" }, { "name": "-r", "content": "Bypass the normal routing tables and send directly to a host on an attached interface. If\nthe host is not on a directly-attached network, an error is returned. This option can be\nused to ping a local host through an interface that has no route through it provided the\noption -I is also used.\n", "flag": "-r" }, { "name": "-R", "content": "ping only. Record route. Includes the RECORDROUTE option in the ECHOREQUEST packet and\ndisplays the route buffer on returned packets. Note that the IP header is only large\nenough for nine such routes. Many hosts ignore or discard this option.\n", "flag": "-R" }, { "name": "-s", "content": "Specifies the number of data bytes to be sent. The default is 56, which translates into\n64 ICMP data bytes when combined with the 8 bytes of ICMP header data.\n", "flag": "-s" }, { "name": "-S", "content": "Set socket sndbuf. If not specified, it is selected to buffer not more than one packet.\n", "flag": "-S" }, { "name": "-t", "content": "ping only. Set the IP Time to Live.\n", "flag": "-t" }, { "name": "-T", "content": "Set special IP timestamp options. timestamp option may be either tsonly (only\ntimestamps), tsandaddr (timestamps and addresses) or tsprespec host1 [host2 [host3\n[host4]]] (timestamp prespecified hops).\n", "flag": "-T" }, { "name": "-U", "content": "Print full user-to-user latency (the old behaviour). Normally ping prints network round\ntrip time, which can be different f.e. due to DNS failures.\n", "flag": "-U" }, { "name": "-v", "content": "Verbose output. Do not suppress DUP replies when pinging multicast address.\n", "flag": "-v" }, { "name": "-V", "content": "Show version and exit.\n", "flag": "-V" }, { "name": "-w", "content": "Specify a timeout, in seconds, before ping exits regardless of how many packets have been\nsent or received. In this case ping does not stop after count packet are sent, it waits\neither for deadline expire or until count probes are answered or for some error\nnotification from network.\n", "flag": "-w" }, { "name": "-W", "content": "Time to wait for a response, in seconds. The option affects only timeout in absence of\nany responses, otherwise ping waits for two RTTs. Real number allowed with dot as a\ndecimal separator (regardless locale setup). 0 means infinite timeout.\n\nWhen using ping for fault isolation, it should first be run on the local host, to verify that\nthe local network interface is up and running. Then, hosts and gateways further and further\naway should be “pinged”. Round-trip times and packet loss statistics are computed. If\nduplicate packets are received, they are not included in the packet loss calculation,\nalthough the round trip time of these packets is used in calculating the\nminimum/average/maximum/mdev round-trip time numbers.\n\nPopulation standard deviation (mdev), essentially an average of how far each ping RTT is from\nthe mean RTT. The higher mdev is, the more variable the RTT is (over time). With a high RTT\nvariability, you will have speed issues with bulk transfers (they will take longer than is\nstrictly speaking necessary, as the variability will eventually cause the sender to wait for\nACKs) and you will have middling to poor VoIP quality.\n\nWhen the specified number of packets have been sent (and received) or if the program is\nterminated with a SIGINT, a brief summary is displayed. Shorter current statistics can be\nobtained without termination of process with signal SIGQUIT.\n\nIf ping does not receive any reply packets at all it will exit with code 1. If a packet count\nand deadline are both specified, and fewer than count packets are received by the time the\ndeadline has arrived, it will also exit with code 1. On other error it exits with code 2.\nOtherwise it exits with code 0. This makes it possible to use the exit code to see if a host\nis alive or not.\n\nThis program is intended for use in network testing, measurement and management. Because of\nthe load it can impose on the network, it is unwise to use ping during normal operations or\nfrom automated scripts.\n", "flag": "-W" } ] }, "ICMP PACKET DETAILS": { "content": "An IP header without options is 20 bytes. An ICMP ECHOREQUEST packet contains an additional\n8 bytes worth of ICMP header followed by an arbitrary amount of data. When a packetsize is\ngiven, this indicates the size of this extra piece of data (the default is 56). Thus the\namount of data received inside of an IP packet of type ICMP ECHOREPLY will always be 8 bytes\nmore than the requested data space (the ICMP header).\n\nIf the data space is at least of size of struct timeval ping uses the beginning bytes of this\nspace to include a timestamp which it uses in the computation of round trip times. If the\ndata space is shorter, no round trip times are given.\n", "subsections": [] }, "DUPLICATE AND DAMAGED PACKETS": { "content": "ping will report duplicate and damaged packets. Duplicate packets should never occur, and\nseem to be caused by inappropriate link-level retransmissions. Duplicates may occur in many\nsituations and are rarely (if ever) a good sign, although the presence of low levels of\nduplicates may not always be cause for alarm.\n\nDamaged packets are obviously serious cause for alarm and often indicate broken hardware\nsomewhere in the ping packet's path (in the network or in the hosts).\n", "subsections": [] }, "TRYING DIFFERENT DATA PATTERNS": { "content": "The (inter)network layer should never treat packets differently depending on the data\ncontained in the data portion. Unfortunately, data-dependent problems have been known to\nsneak into networks and remain undetected for long periods of time. In many cases the\nparticular pattern that will have problems is something that doesn't have sufficient\n“transitions”, such as all ones or all zeros, or a pattern right at the edge, such as almost\nall zeros. It isn't necessarily enough to specify a data pattern of all zeros (for example)\non the command line because the pattern that is of interest is at the data link level, and\nthe relationship between what you type and what the controllers transmit can be complicated.\n\nThis means that if you have a data-dependent problem you will probably have to do a lot of\ntesting to find it. If you are lucky, you may manage to find a file that either can't be sent\nacross your network or that takes much longer to transfer than other similar length files.\nYou can then examine this file for repeated patterns that you can test using the -p option of\nping.\n", "subsections": [] }, "TTL DETAILS": { "content": "The TTL value of an IP packet represents the maximum number of IP routers that the packet can\ngo through before being thrown away. In current practice you can expect each router in the\nInternet to decrement the TTL field by exactly one.\n\nThe TCP/IP specification states that the TTL field for TCP packets should be set to 60, but\nmany systems use smaller values (4.3 BSD uses 30, 4.2 used 15).\n\nThe maximum possible value of this field is 255, and most Unix systems set the TTL field of\nICMP ECHOREQUEST packets to 255. This is why you will find you can “ping” some hosts, but\nnot reach them with telnet(1) or ftp(1).\n\nIn normal operation ping prints the TTL value from the packet it receives. When a remote\nsystem receives a ping packet, it can do one of three things with the TTL field in its\nresponse:\n\n• Not change it; this is what Berkeley Unix systems did before the 4.3BSD Tahoe release.\nIn this case the TTL value in the received packet will be 255 minus the number of routers\nin the round-trip path.\n\n• Set it to 255; this is what current Berkeley Unix systems do. In this case the TTL\nvalue in the received packet will be 255 minus the number of routers in the path from the\nremote system to the pinging host.\n\n• Set it to some other value. Some machines use the same value for ICMP packets that they\nuse for TCP packets, for example either 30 or 60. Others may use completely wild values.\n", "subsections": [] }, "BUGS": { "content": "• Many Hosts and Gateways ignore the RECORDROUTE option.\n\n• The maximum IP header length is too small for options like RECORDROUTE to be\ncompletely useful. There's not much that can be done about this, however.\n\n• Flood pinging is not recommended in general, and flood pinging the broadcast address\nshould only be done under very controlled conditions.\n", "subsections": [] }, "SEE ALSO": { "content": "ip(8), ss(8).\n", "subsections": [] }, "HISTORY": { "content": "The ping command appeared in 4.3BSD.\n\nThe version described here is its descendant specific to Linux.\n\nAs of version s20150815, the ping6 binary doesn't exist anymore. It has been merged into\nping. Creating a symlink named ping6 pointing to ping will result in the same functionality\nas before.\n", "subsections": [] }, "SECURITY": { "content": "ping requires CAPNETRAW capability to be executed 1) if the program is used for non-echo\nqueries (See -N option), or 2) if kernel does not support non-raw ICMP sockets, or 3) if the\nuser is not allowed to create an ICMP echo socket. The program may be used as set-uid root.\n", "subsections": [] }, "AVAILABILITY": { "content": "ping is part of iputils package.\n\n\n\niputils 20211215 PING(8)", "subsections": [] } }, "summary": "ping - send ICMP ECHOREQUEST to network hosts", "flags": [ { "flag": "-4", "long": null, "arg": null, "description": "Use IPv4 only." }, { "flag": "-6", "long": null, "arg": null, "description": "Use IPv6 only." }, { "flag": "-a", "long": null, "arg": null, "description": "Audible ping." }, { "flag": "-A", "long": null, "arg": null, "description": "Adaptive ping. Interpacket interval adapts to round-trip time, so that effectively not more than one (or more, if preload is set) unanswered probe is present in the network. Minimal interval is 200msec unless super-user. On networks with low RTT this mode is essentially equivalent to flood mode." }, { "flag": "-b", "long": null, "arg": null, "description": "Allow pinging a broadcast address." }, { "flag": "-B", "long": null, "arg": null, "description": "Do not allow ping to change source address of probes. The address is bound to one selected when ping starts." }, { "flag": "-c", "long": null, "arg": null, "description": "Stop after sending count ECHOREQUEST packets. With deadline option, ping waits for count ECHOREPLY packets, until the timeout expires." }, { "flag": "-d", "long": null, "arg": null, "description": "Set the SODEBUG option on the socket being used. Essentially, this socket option is not used by Linux kernel." }, { "flag": "-D", "long": null, "arg": null, "description": "Print timestamp (unix time + microseconds as in gettimeofday) before each line." }, { "flag": "-f", "long": null, "arg": null, "description": "Flood ping. For every ECHOREQUEST sent a period “.” is printed, while for every ECHOREPLY received a backspace is printed. This provides a rapid display of how many packets are being dropped. If interval is not given, it sets interval to zero and outputs packets as fast as they come back or one hundred times per second, whichever is more. Only the super-user may use this option with zero interval." }, { "flag": "-F", "long": null, "arg": null, "description": "IPv6 only. Allocate and set 20 bit flow label (in hex) on echo request packets. If value is zero, kernel allocates random flow label." }, { "flag": "-h", "long": null, "arg": null, "description": "Show help." }, { "flag": "-i", "long": null, "arg": null, "description": "Wait interval seconds between sending each packet. Real number allowed with dot as a decimal separator (regardless locale setup). The default is to wait for one second between each packet normally, or not to wait in flood mode. Only super-user may set interval to values less than 2 ms." }, { "flag": "-I", "long": null, "arg": null, "description": "interface is either an address, an interface name or a VRF name. If interface is an address, it sets source address to specified interface address. If interface is an interface name, it sets source interface to specified interface. If interface is a VRF name, each packet is routed using the corresponding routing table; in this case, the -I option can be repeated to specify a source address. NOTE: For IPv6, when doing ping to a link-local scope address, link specification (by the '%'-notation in destination, or by this option) can be used but it is no longer required." }, { "flag": "-l", "long": null, "arg": null, "description": "If preload is specified, ping sends that many packets not waiting for reply. Only the super-user may select preload more than 3." }, { "flag": "-L", "long": null, "arg": null, "description": "Suppress loopback of multicast packets. This flag only applies if the ping destination is a multicast address." }, { "flag": "-m", "long": null, "arg": null, "description": "use mark to tag the packets going out. This is useful for variety of reasons within the kernel such as using policy routing to select specific outbound processing." }, { "flag": "-M", "long": null, "arg": null, "description": "Select Path MTU Discovery strategy. pmtudiscoption may be either do (prohibit fragmentation, even local one), want (do PMTU discovery, fragment locally when packet size is large), or dont (do not set DF flag)." }, { "flag": "-N", "long": null, "arg": null, "description": "IPv6 only. Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request. CAPNETRAW capability is required. help Show help for NI support. name Queries for Node Names. ipv6 Queries for IPv6 Addresses. There are several IPv6 specific flags. ipv6-global Request IPv6 global-scope addresses. ipv6-sitelocal Request IPv6 site-local addresses. ipv6-linklocal Request IPv6 link-local addresses. ipv6-all Request IPv6 addresses on other interfaces. ipv4 Queries for IPv4 Addresses. There is one IPv4 specific flag. ipv4-all Request IPv4 addresses on other interfaces. subject-ipv6=ipv6addr IPv6 subject address. subject-ipv4=ipv4addr IPv4 subject address. subject-name=nodename Subject name. If it contains more than one dot, fully-qualified domain name is assumed. subject-fqdn=nodename Subject name. Fully-qualified domain name is always assumed." }, { "flag": "-n", "long": null, "arg": null, "description": "Numeric output only. No attempt will be made to lookup symbolic names for host addresses." }, { "flag": "-O", "long": null, "arg": null, "description": "Report outstanding ICMP ECHO reply before sending next packet. This is useful together with the timestamp -D to log output to a diagnostic file and search for missing answers." }, { "flag": "-p", "long": null, "arg": null, "description": "You may specify up to 16 “pad” bytes to fill out the packet you send. This is useful for diagnosing data-dependent problems in a network. For example, -p ff will cause the sent packet to be filled with all ones." }, { "flag": "-q", "long": null, "arg": null, "description": "Quiet output. Nothing is displayed except the summary lines at startup time and when finished." }, { "flag": "-Q", "long": null, "arg": null, "description": "Set Quality of Service -related bits in ICMP datagrams. tos can be decimal (ping only) or hex number. In RFC2474, these fields are interpreted as 8-bit Differentiated Services (DS), consisting of: bits 0-1 (2 lowest bits) of separate data, and bits 2-7 (highest 6 bits) of Differentiated Services Codepoint (DSCP). In RFC2481 and RFC3168, bits 0-1 are used for ECN. Historically (RFC1349, obsoleted by RFC2474), these were interpreted as: bit 0 (lowest bit) for reserved (currently being redefined as congestion control), 1-4 for Type of Service and bits 5-7 (highest bits) for Precedence." }, { "flag": "-r", "long": null, "arg": null, "description": "Bypass the normal routing tables and send directly to a host on an attached interface. If the host is not on a directly-attached network, an error is returned. This option can be used to ping a local host through an interface that has no route through it provided the option -I is also used." }, { "flag": "-R", "long": null, "arg": null, "description": "ping only. Record route. Includes the RECORDROUTE option in the ECHOREQUEST packet and displays the route buffer on returned packets. Note that the IP header is only large enough for nine such routes. Many hosts ignore or discard this option." }, { "flag": "-s", "long": null, "arg": null, "description": "Specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data." }, { "flag": "-S", "long": null, "arg": null, "description": "Set socket sndbuf. If not specified, it is selected to buffer not more than one packet." }, { "flag": "-t", "long": null, "arg": null, "description": "ping only. Set the IP Time to Live." }, { "flag": "-T", "long": null, "arg": null, "description": "Set special IP timestamp options. timestamp option may be either tsonly (only timestamps), tsandaddr (timestamps and addresses) or tsprespec host1 [host2 [host3 [host4]]] (timestamp prespecified hops)." }, { "flag": "-U", "long": null, "arg": null, "description": "Print full user-to-user latency (the old behaviour). Normally ping prints network round trip time, which can be different f.e. due to DNS failures." }, { "flag": "-v", "long": null, "arg": null, "description": "Verbose output. Do not suppress DUP replies when pinging multicast address." }, { "flag": "-V", "long": null, "arg": null, "description": "Show version and exit." }, { "flag": "-w", "long": null, "arg": null, "description": "Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop after count packet are sent, it waits either for deadline expire or until count probes are answered or for some error notification from network." }, { "flag": "-W", "long": null, "arg": null, "description": "Time to wait for a response, in seconds. The option affects only timeout in absence of any responses, otherwise ping waits for two RTTs. Real number allowed with dot as a decimal separator (regardless locale setup). 0 means infinite timeout. When using ping for fault isolation, it should first be run on the local host, to verify that the local network interface is up and running. Then, hosts and gateways further and further away should be “pinged”. Round-trip times and packet loss statistics are computed. If duplicate packets are received, they are not included in the packet loss calculation, although the round trip time of these packets is used in calculating the minimum/average/maximum/mdev round-trip time numbers. Population standard deviation (mdev), essentially an average of how far each ping RTT is from the mean RTT. The higher mdev is, the more variable the RTT is (over time). With a high RTT variability, you will have speed issues with bulk transfers (they will take longer than is strictly speaking necessary, as the variability will eventually cause the sender to wait for ACKs) and you will have middling to poor VoIP quality. When the specified number of packets have been sent (and received) or if the program is terminated with a SIGINT, a brief summary is displayed. Shorter current statistics can be obtained without termination of process with signal SIGQUIT. If ping does not receive any reply packets at all it will exit with code 1. If a packet count and deadline are both specified, and fewer than count packets are received by the time the deadline has arrived, it will also exit with code 1. On other error it exits with code 2. Otherwise it exits with code 0. This makes it possible to use the exit code to see if a host is alive or not. This program is intended for use in network testing, measurement and management. Because of the load it can impose on the network, it is unwise to use ping during normal operations or from automated scripts." } ], "examples": [], "see_also": [ { "name": "ip", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/ip/8/json" }, { "name": "ss", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/ss/8/json" } ] }