Net::Ping::External (3pm)

In general:

  use Net::Ping::External qw(ping);
  ping(%options);

Some examples:

use Net::Ping::External qw(ping);

# Ping a single host my $alive = ping(host => "127.0.0.1"); print "127.0.0.1 is online" if $alive;

# Or a list of hosts my @hosts = qw(127.0.0.1 127.0.0.2 127.0.0.3 127.0.0.4); my $num_alive = 0; foreach (@hosts) { $alive = ping(hostname => $_, timeout => 5); print "$_ is alive!\n" if $alive; $num_alive++; } print "$num_alive hosts are alive.\n";

# Using all the fancy options: ping(hostname => "127.0.0.1", count => 5, size => 1024, timeout => 3);

Net::Ping::External is a module which interfaces with the \*(L"ping\*(R" command on many systems. It presently provides a single function, \*(C`ping()\*(C', that takes in a hostname and (optionally) a timeout and returns true if the host is alive, and false otherwise. Unless you have the ability (and willingness) to run your scripts as the superuser on your system, this module will probably provide more accurate results than Net::Ping will.

Why?

• \s-1ICMP\s0 ping is the most reliable way to tell whether a remote host is alive.

• However, Net::Ping cannot use an \s-1ICMP\s0 ping unless you are running your script with privileged (\s-1AKA\s0 \*(L"root\*(R") access.

• The system's \*(L"ping\*(R" command uses \s-1ICMP\s0 and does not usually require privileged access.

• While it is relatively trivial to write a Perl script that parses the output of the \*(L"ping\*(R" command on a given system, the aim of this module is to encapsulate this functionality and provide a single interface for it that works on many systems.

\fIping()\fP \s-1OPTIONS\s0

This module is still \*(L"alpha\*(R"; it is expected that more options to the \*(C`ping()\*(C' function will be added soon.

• \*(C`host, hostname\*(C' The hostname (or dotted-quad \s-1IP\s0 address) of the remote host you are trying to ping. You must specify either the \*(L"hostname\*(R" option or the \*(L"ip\*(R" option. \*(L"host\*(R" and \*(L"hostname\*(R" are synonymous.

• \*(C`ip\*(C' A packed bit-string representing the 4-byte packed \s-1IP\s0 address (as returned by \*(C`Socket.pm\*(C''s \*(C`inet_aton()\*(C' function) of the host that you would like to ping.

• \*(C`timeout\*(C' The maximum amount of time, in seconds, that \*(C`ping()\*(C' will wait for a response. If the remote system does not respond before the timeout has elapsed, \*(C`ping()\*(C' will return false. Default value: 5.

• \*(C`count\*(C' The number of \s-1ICMP\s0 ping packets to send to the remote host. Eventually, Net::Ping::External will return the number of packets that were acknowledged by the remote host; for now, however, \*(C`ping()\*(C' still returns just true or false. Default value: 1.

• \*(C`size\*(C' Specifies the number of data bytes to be sent. The default is 56, which translates into 64 \s-1ICMP\s0 data bytes when combined with the 8 bytes of \s-1ICMP\s0 header data. Default value: 56.

\s-1SUPPORTED\s0 \s-1PLATFORMS\s0

Support currently exists for interfacing with the standard ping utilities on the following systems. Please note that the path to the `ping' should be somewhere in your \s-1PATH\s0 environment variable (or your system's closest equivalent thereof.) Otherwise, Net::Ping::External will be unable to locate your system's `ping' command.

• Win32 Tested \s-1OK\s0 on Win98, Win \s-1XP\s0. It should work on other Windows systems as well.

• Cygwin Tested \s-1OK\s0 on Cygwin 1.5.21. Problem is that we may be running windows ping. They have different options.

• Linux Tested \s-1OK\s0 on Debian 2.2 and Redhat 6.2. It appears that different versions of Linux use different versions of ping, which support different options. Not sure how I'm going to resolve this yet; for now, all the options but \*(C`count\*(C' are disabled.

• \s-1BSD\s0 Tested \s-1OK\s0 on OpenBSD 2.7 and 3.0, Netbsd 1.5.3, Freebsd 4.6.2, 5.4. Needs testing for BSDi.

• Solaris Tested \s-1OK\s0 on Solaris 2.6 and 2.7.

• \s-1IRIX\s0 Tested \s-1OK\s0 on \s-1IRIX\s0 6.5.

• \s-1AIX\s0, \s-1DEC\s0 \s-1OSF\s0, \s-1UNICOSMK\s0, NeXTStep, HP-UX, \s-1BSD/OS\s0 (BSDi), BeOS Support for these systems is integrated into this module but none have been tested yet. If you have successful or unsuccessful test results for any of these systems, please send them to me. On some of these systems, some of the arguments may not be supported. If you'd like to see better support on your system, please e-mail me.

More systems will be added as soon as any users request them. If your system is not currently supported, e-mail me; adding support to your system is probably trivial.

This module should be considered beta. Bugs may exist. Although no specific bugs are known at this time, the module could use testing on a greater variety of systems.

See the warning below.

This module calls whatever \*(L"ping\*(R" program it first finds in your \s-1PATH\s0 environment variable. If your \s-1PATH\s0 contains a trojan \*(L"ping\*(R" program, this module will call that program. This involves a small amount of risk, but no more than simply typing \*(L"ping\*(R" at a system prompt.

Beware Greeks bearing gifts.

Alexandr Ciornii (alexchorny \s-1AT\s0 gmail.com), Colin McMillen (colinm \s-1AT\s0 cpan.org)

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

Dan Moore contributed command-line options and code for NeXT, BeOS, HP-UX, and \s-1BSD/OS\s0.

Jarkko Hietaniemi contributed a huge list of command-line options and results for the `ping' command on 9 different systems.

Randy Moore contributed several patches for Win32 support.

Marc-Andre Dumas contributed a patch for FreeBSD support.

Jonathan Stowe fixed a bug in 0.09 that prevented the module from running on some systems.

Numerous people sent in a patch to fix a bug in 0.10 that broke ping on Windows systems.

Peter N. Lewis contributed a patch that works correctly on Mac \s-1OS\s0 X 10.2 (and hopefully other versions as well).

Net::Ping