This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Paping (pronounced pah ping) is a computer network administration utility used to test the reachability of a host on an Internet Protocol (TCP/IP) network and to measure the time it takes to connect to a specified port. The name is a play on the word ping, another computer network administration utility.
| Developer(s) | Mike Lovell |
|---|---|
| Stable release | 1.5.5
/ April 21, 2011 |
| Operating system | Cross-platform |
| Type | Network-related software |
| License | MIT license |
| Website | code.google.com/p/paping/ |
Because ICMP can be used to identify the operating system of a remote machine,[1][2] it is sometimes blocked.[3][4] If ICMP is blocked, ping cannot be used to identify if the service is responding. Publicly available services must keep their relevant TCP or UDP ports open, paping can attempt to make connections to these ports to determine if a service is responding. Similar utilities such as nmap allow a range of ports to be scanned, however they do not allow you to repetitively scan the same ports.
Paping operates by attempting to connect to an Internet Protocol TCP/IP port on the target. In the process it measures the time taken for a connection to be established and records any connection failures. The results of the test are printed in form of a statistical summary of the connections made including the minimum, maximum, and the mean connection times.
Paping is cross-platform software, currently supporting Windows and Linux.[5]
As of April 2013, the project appears to be abandoned with no new fixes or versions being produced.
Sample paping test
editThe following is a sample output of paping against en.wikipedia.org on TCP/IP port 80 (http) from a Linux host:
./paping -p 80 en.wikipedia.org -c 10
paping v1.5.1 - Copyright (c) 2010 Mike Lovell
Connecting to text.pmtpa.wikimedia.org [208.80.152.2] on TCP 80:
Connected to 208.80.152.2: time=64.11ms protocol=TCP port=80
Connected to 208.80.152.2: time=64.03ms protocol=TCP port=80
Connected to 208.80.152.2: time=65.81ms protocol=TCP port=80
Connected to 208.80.152.2: time=63.56ms protocol=TCP port=80
Connected to 208.80.152.2: time=63.95ms protocol=TCP port=80
Connected to 208.80.152.2: time=64.29ms protocol=TCP port=80
Connected to 208.80.152.2: time=64.35ms protocol=TCP port=80
Connected to 208.80.152.2: time=64.99ms protocol=TCP port=80
Connected to 208.80.152.2: time=63.10ms protocol=TCP port=80
Connected to 208.80.152.2: time=64.02ms protocol=TCP port=80
Connection statistics:
Attempted = 10, Connected = 10, Failed = 0 (0.00%)
Approximate connection times:
Minimum = 63.10ms, Maximum = 65.81ms, Average = 64.22ms
References
edit- ^ "OS Detection over ICMP". Retrieved 29 August 2010.
- ^ "OS Detection over ICMP". doi:10.1109/IIS.2009.53. S2CID 8847655.
{{cite journal}}: Cite journal requires|journal=(help) - ^ "Blocking ICMP in Linux". 2009-11-23. Retrieved 29 August 2010.
- ^ "Nmap Online". Retrieved 13 March 2022.
- ^ "Versions of paping available". Retrieved 10 August 2010.