sc_wartsdump(1) [debian man page]

SC_WARTSDUMP(1) 					    BSD General Commands Manual 					   SC_WARTSDUMP(1)

NAME

     sc_wartsdump -- verbose dump of information contained in a warts file.

SYNOPSIS

     sc_wartsdump [file ...]

DESCRIPTION

     The sc_wartsdump provides a verbose dump of information contained in a sequence of warts files.  While the output is structured and suitable
     for initial analyses of results, the format of the output is not suitable for automated parsing and analysis as the output of sc_wartsdump
     will change overtime with no regard to backwards compatibility.  Analyses of the contents of a warts file should be made using specialised
     programs which link against the scamper file API.

EXAMPLES

     The command:

	sc_wartsdump file1.warts file2.warts

     will decode and print the contents of file1.warts, followed by the contents of file2.warts.

     The command:

	gzcat file1.warts.gz | sc_wartsdump

     will print the contents of the uncompressed file supplied on stdin.

SEE ALSO

     scamper(1), sc_warts2text(1)

AUTHORS

     sc_wartsdump is written by Matthew Luckie <mjl@luckie.org.nz>.

BSD
								 October 15, 2010							       BSD

SC_ALLY(1)						    BSD General Commands Manual 						SC_ALLY(1)

NAME

     sc_ally -- scamper driver to run Ally on a list of candidate aliases.

SYNOPSIS

     sc_ally [-?D] [-i infile] [-o outfile] [-p port] [-U unix-socket] [-w waittime] [-q attempts] [-t logfile]

DESCRIPTION

     The sc_ally utility provides the ability to connect to a running scamper(1) instance and have a set of IPv4 address-pairs testsed for aliases
     using the Ally technique.	For each address pair in the file, sc_ally establishes which probe methods (UDP, TCP-ack, ICMP-echo) solicit an
     incrementing IP-ID value, and then uses the Ally technique on pairs where a probe method is able to obtain an incrementing IP-ID for both
     addresses.  The output is written to a warts file.  The options are as follows:

     -?      prints a list of command line options and a synopsis of each.

     -D      causes sc_ally to detach and become a daemon.

     -i infile
	     specifies the name of the input file which consists of a sequence of IPv4 address-pairs, one pair per line.

     -o outfile
	     specifies the name of the output file to be written.  The output file will use the warts format.

     -p port
	     specifies the port on the local host where scamper(1) is accepting control socket connections.

     -U unix-socket
	     specifies the name of a unix domain socket where scamper(1) is accepting control socket connections.

     -w waittime
	     specifies the minimum length of time, in seconds, to wait between completing a measurement to a particular IP address and issuing the
	     next.

     -q attempts
	     specifies the number of times to try Ally when one of the addresses is unresponsive.

     -t logfile
	     specifies the name of a file to log output from sc_ally generated at run time.

EXAMPLE

     Given a set of IPv4-address pairs in a file named infile.txt:

	192.0.2.1 192.0.32.10
	192.0.2.2 192.0.31.8
	192.0.2.3 192.0.30.64

     and a scamper(1) daemon listening on port 31337, then these address-pairs can be tested for aliases using

     sc_ally -i infile.txt -o outfile.warts -p 31337

SEE ALSO

     N. Spring, R. Mahajan, and D. Wetherall, Measuring ISP topologies with Rocketfuel, Proc. ACM SIGCOMM 2002.  scamper(1), sc_wartsdump(1),
     sc_warts2text(1)

AUTHORS

     sc_ally is written by Matthew Luckie <mjl@luckie.org.nz>.

BSD
								   March 1, 2011							       BSD