sc_ally(1) [debian man page]

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

SC_TRACEDIFF(1) 					    BSD General Commands Manual 					   SC_TRACEDIFF(1)

NAME

     sc_tracediff -- display traceroute paths where the path has changed.

SYNOPSIS

     sc_tracediff [-a] [-m method] [-n] file1.warts file2.warts

DESCRIPTION

     The sc_tracediff utility displays pairs of traceroutes to a destination where the path has changed.  It takes two warts files as input and
     displays paths where a hop differs by its address.  The options are as follows:

     -a      dump all traceroute pairs regardless of whether they have changed.

     -m method
	     specifies the method used to match pairs of traceroutes together.	If dst is specified, traceroutes are matched if the destination IP
	     address of both traces are the same.  If userid is specified, traceroutes are matched if the userid field of both traces are the
	     same.  If dstuserid is specified, traceroutes are matched if the destination IP address and userid fields are the same.  By default,
	     the destination IP address is used.

     -n      names should be reported instead of IP addresses, where possible.

     sc_tracediff can be useful in network monitoring to identify when a forward IP path has changed.  In this scenario, it is recommended that
     Paris traceroute is used with the same UDP source and destination ports for each execution of scamper so that only paths that have changed
     are identified, not merely alternate paths visible due to per-flow load-balancing.  By default scamper uses a source port based on the
     process ID, which will change with each execution of scamper.

EXAMPLES

     The command:

	scamper -O warts -o file1.warts -c 'trace -P udp-paris -s 31337' -f list.txt

     collects the forward IP paths towards a set of IP addresses found in list.txt using 31337 as the UDP source port value.  If the above command
     is adjusted to subsequently collect file2.warts, then we can identify paths that have subsequently changed with the command:

	sc_tracediff file1.warts file2.warts

     If Paris traceroute with ICMP probes is preferred, then the following invocation of scamper is appropriate:

	scamper -O warts -o file1.warts -c 'trace -P icmp-paris -d 31337' -f list.txt

     In this case, scamper uses 31337 as the ICMP checksum value in each probe.

SEE ALSO

     scamper(1),

     B. Augustin, X. Cuvellier, B. Orgogozo, F. Viger, T. Friedman, M. Latapy, C. Magnien, and R. Teixeira, Avoiding traceroute anomalies with
     Paris traceroute, Proc. ACM/SIGCOMM Internet Measurement Conference 2006.

AUTHOR

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

BSD
								  April 21, 2011							       BSD