PythonPing is simple way to ping in Python. With it, you can send ICMP Probes to remote devices like you would do from the terminal. PythonPing is modular, so that you can run it in a script as a standalone function, or integrate its components in a fully-fledged application.
The simplest usage of PythonPing is in a script. You can use the ping
function to ping a target.
If you want to see the output immediately, emulating what happens on the terminal, use the
verbose
flag as below.
from pythonping import ping
ping('127.0.0.1', verbose=True)
This will yeld the following result.
Reply from 127.0.0.1, 9 bytes in 0.17ms
Reply from 127.0.0.1, 9 bytes in 0.14ms
Reply from 127.0.0.1, 9 bytes in 0.12ms
Reply from 127.0.0.1, 9 bytes in 0.12ms
Regardless of the verbose mode, the ping
function will always return a ResponseList
object.
This is a special iterable object, containing a list of Response
items. In each response, you can
find the packet received and some meta information, like the time it took to receive the response
and any error message.
You can also tune your ping by using some of its additional parameters:
size
is an integer that allows you to specify the size of the ICMP payload you desiretimeout
is the number of seconds you wish to wait for a response, before assuming the target is unreachablepayload
allows you to use a specific payload (bytes)count
specify allows you to define how many ICMP packets to sendinterval
the time to wait between pings, in secondssweep_start
andsweep_end
allows you to perform a ping sweep, starting from payload size defined insweep_start
and growing up to size defined insweep_end
. Here, we repeat the payload you provided to match the desired size, or we generate a random one if no payload was provided. Note that if you definedsize
, these two fields will be ignoreddf
is a flag that, if set to True, will enable the Don't Fragment flag in the IP headerverbose
enables the verbose mode, printing output to a stream (seeout
)out
is the target stream of verbose mode. If you enable the verbose mode and do not provideout
, verbose output will be send to thesys.stdout
stream. You may want to use a file here.match
is a flag that, if set to True, will enable payload matching between a ping request and reply (default behaviour follows that of Windows which counts a successful reply by a matched packet identifier only; Linux behaviour counts a non equivalent payload with a matched packet identifier in reply as fail, such as when pinging 8.8.8.8 with 1000 bytes and the reply is truncated to only the first 74 of request payload with a matching packet identifier)
Yes, you need to be root to use pythonping.
All operating systems allow programs to create TCP or UDP sockets without requiring particular permissions. However, ping runs in ICMP (which is neither TCP or UDP). This means we have to create raw IP packets, and sniff the traffic on the network card. Operating systems are designed to require root for such operations. This is because having unrestricted access to the NIC can expose the user to risks if the application running has bad intentions. This is not the case with pythonping of course, but nonetheless we need this capability to create custom IP packets. Unfortunately, there is simply no other way to create ICMP packets.
If you wish to extend PythonPing, or integrate it in your application, we recommend to use the
classes that are part of Python Ping instead of the ping
function. executor.Communicator
handles the communication with the target device, it takes care of sending ICMP requests and
processing responses (note that for it to be thread safe you must then handle making a unique
seed ID for each thread instance, see ping._init_ for an example of this). It ultimately
produces the executor.ResponseList
object. The Communicator
needs to know a target and
which payloads to send to the remote device. For that, we have several classes in the
payload_provider
module. You may want to create your own provider by extending
payload_provider.PayloadProvider
. If you are interested in that, you should check the
documentation of both executor
and payload_provider
module.