SC_PINGER(1)

πŸ“¦
this version Β· 2 versions
  • debian bookworm, debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • opensuse-leap 16.0
, in debian bookworm, debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ¦‹ SC_PINGER(1) β€” the general commands manual, but make it cute

okay bestie, so sc_pinger lives in the General Commands Manual section of your system, and it's literally the little scamper driver that goes around pinging a whole list of addresses for you. no cap. πŸ’…


✨ NAME ✨

sc_pinger β€” it's the scamper driver that runs ping with different probe methods on a list of addresses. that's it, that's the vibe. πŸŽ€


🌸 SYNOPSIS 🌸

sc_pinger [-?D] [-a infile] [-o outfile] [-p port] [-U unix-socket]
          [-c probe-count] [-m method] [-t logfile]

look at her. so compact. so iconic. πŸ‘‘


πŸ’– DESCRIPTION πŸ’–

okay so sc_pinger is the utility that lets you hook up to an already-running scamper(1) instance and run ping on a whole set of IPv4 and IPv6 addresses. multitasking queen. 🌈

for each address in the file, sc_pinger will try the ICMP, UDP, and TCP-ack probe methods to try and solicit responses from that address. and here's the smart part β€” sc_pinger will not try all the methods if one method already gets responses. she's efficient, she knows when to stop, main character energy fr. πŸ’…

the output of sc_pinger gets written to a warts(5) file, which you can then process to extract all the deets of the responses. slay.

the options are as follows:

  • -? β€” prints a list of command line options and a synopsis of each. the little "help me" button, we love her. 🫢
  • -D β€” causes sc_pinger to detach and become a daemon. she's leaving the group chat to go be mysterious. πŸ’€
  • -a infile β€” specifies the name of the input file, which consists of a sequence of IPv4 and IPv6 addresses, one per line. no commas, no chaos, just one address per line bestie. πŸ“
  • -o outfile β€” specifies the name of the output file to be written. heads up: the output file will use the warts(5) format. ✨
  • -p port β€” specifies the port on the local host where scamper(1) is accepting control socket connections. knock knock, it's me. πŸšͺ
  • -U unix-socket β€” specifies the name of a unix domain socket where scamper(1) is accepting control socket connections. the introvert's version of -p, honestly. 🧚
  • -c probe-count β€” specifies the number of probes to send for each method. and sc_pinger accepts two formats, so pay attention:
    • 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. yes, she has standards. πŸ’…

  • -m method β€” specifies a single probe method to try. the available probe methods are the same as scamper's ping implementation, listed in the scamper(1) manual page. by default, sc_pinger uses ICMP-echo, UDP-dport, and TCP-ack-sport to destination port 80. the default trio. the holy trinity. πŸ”₯
  • -t logfile β€” specifies the name of a file to log output from sc_pinger generated at run time. receipts, bestie. always keep the receipts. 🧾

🌈 EXAMPLES 🌈

okay so say you've got a set of IPv4 and IPv6 address sets in a file named infile.txt:

192.0.2.1
192.0.32.10
192.0.31.60
2001:db8::1

and a scamper(1) daemon listening on port 31337, then these addresses can be probed using:

sc_pinger -a infile.txt -o outfile.warts -p 31337

to send 4 probes, and stop after receiving two responses:

sc_pinger -a infile.txt -o outfile.warts -p 31337 -c 2/4

to use ICMP-echo and TCP-syn probes to destination port 443:

sc_pinger -a infile.txt -o outfile.warts -p 31337 -m icmp-echo -m
'tcp-syn -d 443'

(and yes, that last one wraps like that in the original too β€” the -m 'tcp-syn -d 443' is one quoted argument, so keep the quotes exactly as they are, bestie. the shell is counting on you. πŸ™ˆ)


πŸ‘‘ SEE ALSO πŸ‘‘

scamper(1), sc_wartsdump(1), sc_warts2json(1), sc_warts2text(1)

the whole friend group. go say hi. 🫢


πŸ’œ AUTHORS πŸ’œ

sc_pinger was written by Matthew Luckie <mjl@luckie.org.nz>. king behaviour, honestly. πŸ‘‘


ngl that's the whole page. every flag, every default, every example β€” nothing skipped, nothing invented. periodt. πŸ’…

and that's a wrap on the sc_pinger(1) page from the Debian build, dated Jun 24, 2020. thanks for reading the whole thing bestie, you ate that. πŸ“βœ¨πŸ¦‹