SC_RADARGUN(1)

πŸ’… SC_RADARGUN(1) β€” the girlies' guide to radargun πŸ’…

okay so bestie, this is sc_radargun from the General Commands Manual, and it's genuinely one of my faves. it's a scamper(1) driver that runs radargun on a list of candidate aliases. no cap, that's the whole vibe.


✨ NAME ✨

sc_radargun β€” it's the scamper driver that runs radargun on a list of candidate aliases 🫢


🌈 SYNOPSIS 🌈

sc_radargun [-?D] [-a infile] [-f fudge] [-o outfile] [-O options]
            [-p port] [-P pps] [-q attempts] [-r wait-round]
            [-R round-count] [-t logfile] [-U unix]

sc_radargun [-d dump] data-file

like, two whole modes. two. main character energy fr fr πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so sc_radargun is that girl: it gives you the ability to connect to a running scamper(1) instance and figure out which of the IPv4 addresses you hand it are actually aliases, using the Radargun technique. periodt.

here's the tea πŸ“ β€” for all the addresses in your file, sc_radargun first establishes which probe methods (that's UDP, TCP-ack, ICMP-echo) actually solicit an incrementing IP-ID value. then, for the addresses where some probe method is able to get that incrementing IP-ID, it runs the Radargun technique on them. the output gets written to a warts file.

the options are as follows, and yes we're going through all of them because I love you πŸ’–

✨ OPTIONS ✨

  • -? β€” prints a list of command line options and a synopsis of each. a little menu, a little appetizer πŸ’…
  • -D β€” causes sc_radargun 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 list of IPv4 addresses. the file can either contain sets to test, one set per line, or simply one set, one address per line. both are valid, choose your own adventure 🌸
  • -d dump β€” specifies the dump ID to use to analyze the collected data. current choices for this option are:
    • 1: dump inferred aliases.
    • 2: dump interface classifications.
  • -f fudge β€” specifies the fudge to use when inferring if a device is deriving IP-ID values from a counter. by default, responses the maximum difference between two samples must be no larger than 5000. the fudge value also impacts alias inference. if a value of zero is used, the IP-ID samples must simply be in order. cute, simple, no math πŸŽ€
  • -o outfile β€” specifies the name of the output file to be written. the output file will use the warts format. iconic format ngl ✨
  • -O options β€” lets you tailor sc_radargun's behavior even further. current choices for this option are:
    • nobs: do not consider if IP-ID values might be byte-swapped in the header
    • nobudget: do not consider if the radargun measurement can complete in the round time give the packets-per-second rate specified.
    • noradargun: do not conduct radargun step. stop after classifying interface IP-ID behavior.
    • noreserved: do not probe reserved IP addresses.
    • rows: the addresses in the input file are supplied in rows, and the radargun measurements will probe and evaluate each set independently.
    • tc: when dumping candidate aliases, report the transitive closure, rather than pairs in isolation.
  • -p port β€” specifies the port on the local host where scamper(1) is accepting control socket connections. knock knock bestie πŸ‘‘
  • -P pps β€” specifies the packets-per-second rate that scamper is running at. the PPS value is used to infer if the radargun measurement can fit in scamper's probe budget. very budget-conscious of her πŸ’œ
  • -q attempts β€” specifies the number of probe packets to use to when inferring if an IP address assigns IP-ID values from a counter.
  • -r wait-round β€” specifies the length of time, in seconds, each round should aim to complete in. by default, 30 seconds.
  • -R round-count β€” specifies the number of rounds to pursue in radargun. by default, 30 rounds.
  • -t logfile β€” specifies the name of a file to log progress output from sc_radargun generated at run time. receipts, but make them a text file πŸ“
  • -U unix β€” specifies the name of a unix domain socket where a local scamper(1) instance is accepting control socket connections.

πŸ”₯ EXAMPLES πŸ”₯

sc_radargun requires a scamper(1) instance listening on a port for commands in order to collect data, at 20 packets per second:

scamper -P 31337 -p 20

that will start a scamper(1) instance listening on port 31337 on the loopback interface. okay so now say you wanna use sc_radargun to infer which addresses might be aliases, listed in a file named set-1.txt:

192.0.2.2
192.0.32.10
192.0.30.64
192.0.31.8

the following command will test these IP addresses for aliases using ICMP, UDP, and TCP probes (as appropriate) using the radargun technique with 10 rounds, each round taking 4 seconds:

sc_radargun -a set-1.txt -o set-1.warts -p 20 -r 4 -R 10

now let's say you wanna infer which addresses might be aliases, listed in a file named set-2.txt organized as sets of candidate aliases to test:

192.0.2.2 192.0.32.10 192.0.30.64 192.0.31.8
192.0.2.3 192.0.32.11 192.0.30.65 192.0.31.9

the following command will test these organized sets of IP addresses for aliases:

sc_radargun -a set-2.txt -o set-2.warts -p 20 -O rows

and if you wanna use data previously collected with sc_radargun and stored in set-2.warts, to infer likely aliases, reported in pairs:

sc_radargun -d 1 set-2.warts

and finally, to use data previously collected with sc_radargun and stored in set-2.warts, to report interface IP-ID classifications:

sc_radargun -d 2 set-2.warts

ate. no crumbs left πŸ“βœ¨


πŸ’– SEE ALSO πŸ’–

like the whole friend group. go read them, iykyk πŸ¦‹


πŸ‘‘ AUTHORS πŸ‘‘

sc_radargun was written by Matthew Luckie <mjl@luckie.org.nz>, but the original implementation was by Bender et al. shoutout to the originators, fr fr πŸ’œ


bestie, this page came to you from Debian, dated November 21, 2017 β€” that's the version and date, and I'm blowing them a little kiss goodbye πŸ’‹ bye pookie, go infer some aliases 🌈⭐