Ping (networking utility)

Last updated

Ping
Original author(s) Mike Muuss
Developer(s) Various open-source and commercial developers
Initial release1983;41 years ago (1983)
Platform Cross-platform
Type Command
License Public-domain, BSD, GPL, MIT

ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It is available for virtually all operating systems that have networking capability, including most embedded network administration software.

Contents

Ping measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source. The name comes from active sonar terminology that sends a pulse of sound and listens for the echo to detect objects under water. [1]

Ping operates by means of Internet Control Message Protocol (ICMP) packets. Pinging involves sending an ICMP echo request to the target host and waiting for an ICMP echo reply. The program reports errors, packet loss, and a statistical summary of the results, typically including the minimum, maximum, the mean round-trip times, and standard deviation of the mean.

The command-line options of the ping utility and its output vary between the numerous implementations. Options may include the size of the payload, count of tests, limits for the number of network hops (TTL) that probes traverse, interval between the requests and time to wait for a response. Many systems provide a companion utility ping6, for testing on Internet Protocol version 6 (IPv6) networks, which implement ICMPv6.

History

DOS version of ping Cmd-ping.png
DOS version of ping

The ping utility was written by Mike Muuss in December 1983 during his employment at the Ballistic Research Laboratory, now the US Army Research Laboratory. A remark by David Mills on using ICMP echo packets for IP network diagnosis and measurements prompted Muuss to create the utility to troubleshoot network problems. [1] The author named it after the sound that sonar makes since its methodology is analogous to sonar's echolocation. [1] [2] The backronym Packet InterNet Groper for PING has been used for over 30 years, and although Muuss says that from his point of view, PING was not intended as an acronym, he has acknowledged Mills' expansion of the name. [1] [3] The first released version was public domain software; all subsequent versions have been licensed under the BSD license. Ping was first included in 4.3BSD. [4] The FreeDOS version was developed by Erick Engelke and is licensed under the GPL. [5] Tim Crawford developed the ReactOS version. It is licensed under the MIT License. [6]

Any host must process ICMP echo requests and issue echo replies in return. [7]

Invocation example

The following is the output of running ping on Linux for sending five probes (1-second interval by default, configurable via -i option) to the target host www.example.com:

$ ping-c5www.example.com  PING www.example.com (93.184.216.34): 56 data bytes64 bytes from 93.184.216.34: icmp_seq=0 ttl=56 time=11.632 ms64 bytes from 93.184.216.34: icmp_seq=1 ttl=56 time=11.726 ms64 bytes from 93.184.216.34: icmp_seq=2 ttl=56 time=10.683 ms64 bytes from 93.184.216.34: icmp_seq=3 ttl=56 time=9.674 ms64 bytes from 93.184.216.34: icmp_seq=4 ttl=56 time=11.127 ms--- www.example.com ping statistics ---5 packets transmitted, 5 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 9.674/10.968/11.726/0.748 ms

The output lists each probe message and the results obtained. Finally, it lists the statistics of the entire test. In this example, the shortest round-trip time was 9.674 ms, the average was 10.968 ms, and the maximum value was 11.726 ms. The measurement had a standard deviation of 0.748 ms.

Error indications

In cases of no response from the target host, most implementations display either nothing or periodically print notifications about timing out. Possible ping results indicating a problem include the following:

In case of error, the target host or an intermediate router sends back an ICMP error message, for example host unreachable or TTL exceeded in transit. In addition, these messages include the first eight bytes of the original message (in this case header of the ICMP echo request, including the quench value), so the ping utility can match responses to originating queries. [8]

Message format

ICMP packet transported with IPv4

An ICMP packet transported with IPv4 looks like this.

IPv4 datagram
Offset Octet 0123
Octet Bit 012345678910111213141516171819202122232425262728293031
00Version (4)IHL (5)DSCP (0)ECN (0)Total Length
432IdentificationFlagsFragment Offset
864Time to LiveProtocol (1)Header Checksum
1296Source address
16128Destination address
ICMP Echo Request packet
20160Type (0)Code (0)Checksum
24192IdentifierSequence Number
28224(Payload)
32256
⋮⋮
Type: 8 bits:Set to 0 to indicate 'Echo Request'.
Checksum: 16 bits:Checksum is the 16-bit ones' complement of the ones' complement sum of the ICMP packet, starting with the Type field, [9] including the Payload. The IP header is not included.
Identifier: 16 bits:Can be used by the client to match the reply with the request that caused the reply.
Sequence Number: 16 bits:Can be used by the client to match the reply with the request that caused the reply.
Payload: Variable:Optional. Payload for the different kind of answers; can be an arbitrary length, left to implementation detail.

Most Linux systems use a unique Identifier for every ping process, and Sequence Number is an increasing number within that process. Windows uses a fixed Identifier, which varies between Windows versions, and a Sequence Number that is only reset at boot time.

The Echo Reply is returned as:

ICMP Echo Reply packet
20160Type (8)Code (0)Checksum
24192IdentifierSequence Number
28224(Payload)
32256
⋮⋮
Type: 8 bits:Set to 8 to indicate 'Echo Reply'.
Identifier: 16 bits:Copied from the Echo Request and returned.
Sequence Number: 16 bits:Copied from the Echo Request and returned.
Payload: Variable:Optional. Payload is copied from the Echo Request and returned.

ICMPv6 packet transported with IPv6

An ICMP packet transported with IPv6 looks like this.

IPv6 datagram
Offset Octet 0123
Octet Bit 012345678910111213141516171819202122232425262728293031
00Version (6)Traffic classFlow label
432Payload lengthNext header (58)Hop limit
864Source address
1296
16128
20160
24192Destination address
28224
32256
36288
ICMPv6 Echo Request packet
40320Type (128)Code (0)Checksum
44352IdentifierSequence Number
48384(Payload)
52416
⋮⋮
Type: 8 bits:Set to 128 to indicate 'Echo Request'.
Identifier: 16 bits:Can be used by the client to match the reply with the request that caused the reply.
Sequence Number: 16 bits:Can be used by the client to match the reply with the request that caused the reply.
Checksum: 16 bits:The checksum is calculated from the ICMP message (starting with the Type field), prepended with an IPv6 pseudo-header. [10]
Payload: Variable:Optional. Payload for the different kind of answers; can be an arbitrary length, left to implementation detail.

Most Linux systems use a unique Identifier for every ping process, and Sequence Number is an increasing number within that process. Windows uses a fixed Identifier, which varies between Windows versions, and a Sequence Number that is only reset at boot time.

The Echo Reply is returned as:

ICMPv6 Echo Reply packet
40320Type (129)Code (0)Checksum
44352IdentifierSequence Number
48384(Payload)
52416
⋮⋮
Type: 8 bits:Set to 129 to indicate 'Echo Reply'.
Identifier: 16 bits:Copied from the Echo Request and returned.
Sequence Number: 16 bits:Copied from the Echo Request and returned.
Payload: Variable:Optional. Payload is copied from the Echo Request and returned.

Payload

The payload of the packet is generally filled with ASCII characters, as the output of the tcpdump utility shows in the last 32 bytes of the following example (after the eight-byte ICMP header starting with 0x0800):

16:24:47.966461IP(tos0x0,ttl128,id15103,offset0,flags[none],proto:ICMP(1),length:60)192.168.146.22>192.168.144.5:ICMPechorequest,id1,seq38,length400x0000:4500003c3aff000080015c55c0a89216E..<:.....\U....0x0010:c0a8900508004d350001002661626364......M5...&abcd0x0020:65666768696a6b6c6d6e6f7071727374efghijklmnopqrst0x0030:757677616263646566676869        uvwabcdefghi

The payload may include a timestamp indicating the time of transmission and a sequence number, which are not found in this example. This allows ping to compute the round-trip time in a stateless manner without needing to record the time of transmission of each packet.

The payload may also include a magic packet for the Wake-on-LAN protocol, but the minimum payload, in that case, is longer than shown. The Echo Request typically does not receive any reply if the host was sleeping in hibernation state, but the host still wakes up from sleep state if its interface is configured to accept wakeup requests. If the host is already active and configured to allow replies to incoming ICMP Echo Request packets, the returned reply should include the same payload. This may be used to detect that the remote host was effectively woken up, by repeating a new request after some delay to allow the host to resume its network services. If the host was just sleeping in low power active state, a single request wakes up that host just enough to allow its Echo Reply service to reply instantly if that service was enabled. The host does not need to wake up all devices completely and may return to low-power mode after a short delay. Such configuration may be used to avoid a host to enter in hibernation state, with much longer wake-up delay, after some time passed in low power active mode.[ citation needed ]

A packet including IP and ICMP headers must not be greater than the maximum transmission unit of the network, or risk being fragmented.

Security loopholes

To conduct a denial-of-service attack, an attacker may send ping requests as fast as possible, possibly overwhelming the victim with ICMP echo requests. This technique is called a ping flood. [11]

Ping requests to multiple addresses, ping sweeps, may be used to obtain a list of all hosts on a network.

See also

Related Research Articles

The Internet Control Message Protocol (ICMP) is a supporting protocol in the Internet protocol suite. It is used by network devices, including routers, to send error messages and operational information indicating success or failure when communicating with another IP address. For example, an error is indicated when a requested service is not available or that a host or router could not be reached. ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to exchange data between systems, nor is it regularly employed by end-user network applications.

<span class="mw-page-title-main">IPv4</span> Fourth version of the Internet Protocol

Internet Protocol version 4 (IPv4) is the first version of the Internet Protocol (IP) as a standalone specification. It is one of the core protocols of standards-based internetworking methods in the Internet and other packet-switched networks. IPv4 was the first version deployed for production on SATNET in 1982 and on the ARPANET in January 1983. It is still used to route most Internet traffic today, even with the ongoing deployment of Internet Protocol version 6 (IPv6), its successor.

The Internet Protocol (IP) is the network layer communications protocol in the Internet protocol suite for relaying datagrams across network boundaries. Its routing function enables internetworking, and essentially establishes the Internet.

In computer networking, the maximum transmission unit (MTU) is the size of the largest protocol data unit (PDU) that can be communicated in a single network layer transaction. The MTU relates to, but is not identical to the maximum frame size that can be transported on the data link layer, e.g., Ethernet frame.

The Transmission Control Protocol (TCP) is one of the main protocols of the Internet protocol suite. It originated in the initial network implementation in which it complemented the Internet Protocol (IP). Therefore, the entire suite is commonly referred to as TCP/IP. TCP provides reliable, ordered, and error-checked delivery of a stream of octets (bytes) between applications running on hosts communicating via an IP network. Major internet applications such as the World Wide Web, email, remote administration, and file transfer rely on TCP, which is part of the Transport layer of the TCP/IP suite. SSL/TLS often runs on top of TCP.

In computing, traceroute and tracert are diagnostic command-line interface commands for displaying possible routes (paths) and transit delays of packets across an Internet Protocol (IP) network.

Time to live (TTL) or hop limit is a mechanism which limits the lifespan or lifetime of data in a computer or network. TTL may be implemented as a counter or timestamp attached to or embedded in the data. Once the prescribed event count or timespan has elapsed, data is discarded or revalidated. In computer networking, TTL prevents a data packet from circulating indefinitely. In computing applications, TTL is commonly used to improve the performance and manage the caching of data.

In computer networking, the User Datagram Protocol (UDP) is one of the core communication protocols of the Internet protocol suite used to send messages to other hosts on an Internet Protocol (IP) network. Within an IP network, UDP does not require prior communication to set up communication channels or data paths.

<span class="mw-page-title-main">IP over Avian Carriers</span> Proposal to carry IP traffic by birds

In computer networking, IP over Avian Carriers (IPoAC) is a joke proposal to carry Internet Protocol (IP) traffic by birds such as homing pigeons. IP over Avian Carriers was initially described in RFC 1149 issued by the Internet Engineering Task Force, written by David Waitzman, and released on April 1, 1990. It is one of several April Fools' Day Request for Comments.

The Address Resolution Protocol (ARP) is a communication protocol used for discovering the link layer address, such as a MAC address, associated with a given internet layer address, typically an IPv4 address. This mapping is a critical function in the Internet protocol suite. ARP was defined in 1982 by RFC 826, which is Internet Standard STD 37.

<span class="mw-page-title-main">Network address translation</span> Technique for making connections between IP address spaces

Network address translation (NAT) is a method of mapping an IP address space into another by modifying network address information in the IP header of packets while they are in transit across a traffic routing device. The technique was originally used to bypass the need to assign a new address to every host when a network was moved, or when the upstream Internet service provider was replaced, but could not route the network's address space. It has become a popular and essential tool in conserving global address space in the face of IPv4 address exhaustion. One Internet-routable IP address of a NAT gateway can be used for an entire private network.

A Smurf attack is a distributed denial-of-service attack in which large numbers of Internet Control Message Protocol (ICMP) packets with the intended victim's spoofed source IP are broadcast to a computer network using an IP broadcast address. Most devices on a network will, by default, respond to this by sending a reply to the source IP address. If the number of machines on the network that receive and respond to these packets is very large, the victim's computer will be flooded with traffic. This can slow down the victim's computer to the point where it becomes impossible to work on.

A ping of death is a type of attack on a computer system that involves sending a malformed or otherwise malicious ping to a computer. In this attack, a host sends hundreds of ping requests with a packet size that is large or illegal to another host to try to take it offline or to keep it preoccupied responding with ICMP Echo replies.

The link-state advertisement (LSA) is a basic communication means of the OSPF routing protocol for the Internet Protocol (IP). It communicates the router's local routing topology to all other local routers in the same OSPF area. OSPF is designed for scalability, so some LSAs are not flooded out on all interfaces, but only on those that belong to the appropriate area. In this way detailed information can be kept localized, while summary information is flooded to the rest of the network. The original IPv4-only OSPFv2 and the newer IPv6-compatible OSPFv3 have broadly similar LSA types.

Internet Control Message Protocol version 6 (ICMPv6) is the implementation of the Internet Control Message Protocol (ICMP) for Internet Protocol version 6 (IPv6). ICMPv6 is an integral part of IPv6 and performs error reporting and diagnostic functions.

<span class="mw-page-title-main">Idle scan</span>

An idle scan is a TCP port scan method for determining what services are open on a target computer without leaving traces pointing back at oneself. This is accomplished by using packet spoofing to impersonate another computer so that the target believes it's being accessed by the zombie. The target will respond in different ways depending on whether the port is open, which can in turn be detected by querying the zombie.

IP fragmentation attacks are a kind of computer security attack based on how the Internet Protocol (IP) requires data to be transmitted and processed. Specifically, it invokes IP fragmentation, a process used to partition messages from one layer of a network into multiple smaller payloads that can fit within the lower layer's protocol data unit (PDU). Every network link has a maximum size of messages that may be transmitted, called the maximum transmission unit (MTU). If the SDU plus metadata added at the link layer exceeds the MTU, the SDU must be fragmented. IP fragmentation attacks exploit this process as an attack vector.

The Internet checksum, also called the IPv4 header checksum is a checksum used in version 4 of the Internet Protocol (IPv4) to detect corruption in the header of IPv4 packets. It is carried in the IP packet header, and represents the 16-bit result of summation of the header words.

BWPing is a tool to measure bandwidth and response times between two hosts using Internet Control Message Protocol (ICMP) echo request/echo reply mechanism. It does not require any special software on the remote host. The only requirement is the ability to respond on ICMP echo request messages. BWPing supports both IPv4 and IPv6 networks.

An IPv6 packet is the smallest message entity exchanged using Internet Protocol version 6 (IPv6). Packets consist of control information for addressing and routing and a payload of user data. The control information in IPv6 packets is subdivided into a mandatory fixed header and optional extension headers. The payload of an IPv6 packet is typically a datagram or segment of the higher-level transport layer protocol, but may be data for an internet layer or link layer instead.

References

  1. 1 2 3 4 Mike Muuss. "The Story of the PING Program". U.S. Army Research Laboratory. Archived from the original on 25 October 2019. Retrieved 8 September 2010. My original impetus for writing PING for 4.2a BSD UNIX came from an offhand remark in July 1983 by Dr. Dave Mills ... I named it after the sound that a sonar makes, inspired by the whole principle of echo-location ... From my point of view PING is not an acronym standing for Packet InterNet Grouper, it's a sonar analogy. However, I've heard second-hand that Dave Mills offered this expansion of the name, so perhaps we're both right.
  2. ↑ Salus, Peter (1994). A Quarter Century of UNIX. Addison-Wesley. ISBN   978-0-201-54777-1.
  3. ↑ Mills, D.L. (December 1983). Internet Delay Experiments. IETF. doi: 10.17487/RFC0889 . RFC 889 . Retrieved 26 November 2019.
  4. ↑ "man page ping section 8". www.manpagez.com.
  5. ↑ "ibiblio.org FreeDOS Package -- ping (Networking)". www.ibiblio.org.
  6. ↑ "GitHub - reactos/reactos: A free Windows-compatible Operating System". 8 August 2019 – via GitHub.
  7. ↑ R. Braden, ed. (October 1989). Requirements for Internet Hosts -- Communication Layers. Network Working Group. doi: 10.17487/RFC1122 . STD 3. RFC 1122.Internet Standard 3. Updated by RFC  1349, 4379, 5884, 6093, 6298, 6633, 6864, 8029 and 9293. Every host MUST implement an ICMP Echo server function that receives Echo Requests and sends corresponding Echo Replies.
  8. ↑ "ICMP: Internet Control Message Protocol". repo.hackerzvoice.net. 13 January 2000. Archived from the original on 4 August 2016. Retrieved 4 December 2014.
  9. ↑ "RFC Sourcebook's page on ICMP". Archived from the original on 6 July 2018. Retrieved 20 December 2010.
  10. ↑ A. Conta; S. Deering (March 2006). M. Gupta (ed.). Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification. Network Working Group. doi: 10.17487/RFC4443 . STD 89. RFC 4443.Internet Standard 89. Obsoletes RFC  2463. Updates RFC  2780. Updated by RFC  4884.
  11. ↑ "What is a Ping Flood | ICMP Flood | DDoS Attack Glossary | Imperva". Learning Center. Retrieved 26 July 2021.

Further reading

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.