The sc_pinger utility provides the ability to connect to a running scamper(1) instance and run ping on a
set of IPv4 and IPv6 addresses. For each address in the file, sc_pinger will try ICMP, UDP, and TCP-ack
probe methods to solicit responses from the address. sc_pinger will not try all methods if one method
obtains responses. The output of sc_pinger is written to a warts(5) file, which can then be processed to
extract details of responses. The options are as follows:
-? prints a list of command line options and a synopsis of each.
-D causes sc_pinger to detach and become a daemon.
-ainfile
specifies the name of the input file which consists of a sequence of IPv4 and IPv6 addresses, one
per line.
-ooutfile
specifies the name of the output file to be written. The output file will use the warts(5)
format.
-pport
specifies the port on the local host where scamper(1) is accepting control socket connections.
-Uunix-socket
specifies the name of a unix domain socket where scamper(1) is accepting control socket
connections.
-cprobe-count
specifies the number of probes to send for each method. sc_pinger accepts two formats: a single
integer that specifies the number of probes (and responses) desired; or, two integers, separated
by /, that specify the number of responses desired and maximum number of probes to send. By
default, sc_pinger seeks three responses from up to five probes.
-mmethod
specifies a single probe method to try. The available probe methods are the same as scamper's
ping implementation, listed in scamper(1) manual page. By default, sc_pinger uses ICMP-echo,
UDP-dport, and TCP-ack-sport to destination port 80.
-tlogfile
specifies the name of a file to log output from sc_pinger generated at run time.