SC_BDRMAP(1) | General Commands Manual | SC_BDRMAP(1) |
sc_bdrmap
—
scamper driver to map first hop border routers of
networks
sc_bdrmap |
[-6ADi ]
[-a ip2as-file]
[-c allyconf]
[-C flowid]
[-f firsthop]
[-l log-file]
[-M ipmap-file]
[-o output-file]
[-O option]
[-p port]
[-U unix]
[-R unix]
[-S srcaddr]
[-v vpases]
[-x ixp-file] |
sc_bdrmap |
[-6 ]
[-a ip2as-file]
[-d dump]
[-g delegated-file]
[-M ipmap-file]
[-n names-file]
[-r relationships-file]
[-v vpases]
[-x ixp-file]
[file ...] |
The sc_bdrmap
utility provides the ability
to connect to a running scamper(1) instance and use it to
map the first hop border routers of networks using the "bdrmap"
technique. sc_bdrmap
uses targeted traceroutes,
alias resolution techniques, knowledge of traceroute idiosyncrasies, and
codification of topologicial constraints in a structured set of constraints,
to correctly identify interdomain links at the granularity of individual
border routers. sc_bdrmap
operates in two distinct
modes: data collection, and data analysis.
In the data collection mode, sc_bdrmap
uses Paris traceroute with ICMP-echo probes to trace the paths towards every
distinct address block, using a stop-set to avoid re-probing portions of
paths that do not provide useful constraints for the first hop border
routers, as well as alias resolution techniques (Mercator, Ally, Prefixscan,
and the Too-Big-Trick) to collapse the interface graph into a router-level
topology. sc_bdrmap
will also use probes with the
record-route and pre-specified timestamp IP-level options to collect
additional information on the return path from a router, where the probes
are usable.
In the data analysis mode, sc_bdrmap
uses
the collected data to infer a router-level topology of the hosting network
and the interconnecting routers belonging to the hosting network's
neighbors.
The supported options to sc_bdrmap
are as
follows:
-6
sc_bdrmap
should infer IPv6 border
routers, and that the input files are for the IPv6 topology. This feature
is currently work in progress.-a
ip2as-filesc_bdrmap
should use when collecting and analysing
topology data. See the examples section for a description of how this file
must be formatted.-A
sc_bdrmap
should collect data towards. This option is useful for testing and
debugging.-c
allyconfsc_bdrmap
should repeat pair-wise alias inferences that were made implying a central
shared IP-ID counter. By default, each pair of aliases is tested five
additional times at 5 minute intervals because two IP addresses belonging
to two different routers could happen to return IP-ID values that imply a
central shared IP-ID counter.-C
flowid-d
dump-D
sc_bdrmap
to detach and become a
daemon.-f
firsthopsc_bdrmap
should begin at when collecting
traceroute paths. If sc_bdrmap
is being run behind
a NAT router, the private IP address of that router is uninteresting, and
this option allows that hop to be skipped.-g
delegated-filesc_bdrmap
to allow inferences in the analysis
phase of who operates unrouted IP address space.-i
sc_bdrmap
should
collect data towards. This option is useful for testing and
debugging.-l
log-filesc_bdrmap
generated at run time.-M
ipmap-file-n
names-file-o
output-file-O
optionsc_bdrmap
to be further
tailored. The current choices for this option are:
-p
port-r
relationships-file-R
unix-S
srcaddr-U
unix-v
vpases-x
ixp-fileGiven a set of prefixes with origin AS in a file named ip2as.txt, a list of VP ases in vpases.txt, a list of IXP prefixes in ixp.txt, and a scamper(1) instance listening on port 31337 configured to probe at 100 packets per second started as follows:
scamper -P 31337 -p 100
the following command will collect raw topology data to support inference of border routers for the network hosting the vantage point, storing raw data into bdrmap.warts, and logging run-time information into logfile1.txt:
sc_bdrmap -p 31337 -o bdrmap.warts -l
logfile1.txt -a ip2as.txt -v vpases.txt -x ixp.txt
To infer border routers from the collected data, using the same input files as above, with a set of AS relationships contained in asrel.txt, and a set of prefix delegations assembled from the Regional Internet Registry (RIR) Statistics files in delegated.txt:
sc_bdrmap -d routers -a ip2as.txt -g
delegated.txt -r asrel.txt -v vpases.txt -x ixp.txt bdrmap.warts
>bdrmap.routers.txt
To view annotated traceroutes stored in bdrmap.warts with IP to DNS names information stored in names.txt:
sc_bdrmap -d traces -a ip2as.txt -v
vpases.txt -x ixp.txt -n names.txt bdrmap.wart
>bdrmap.traces.txt
scamper(1), sc_ally(1), sc_speedtrap(1), sc_wartsdump(1), sc_warts2text(1), sc_warts2json(1)
M. Luckie, A. Dhamdhere, B. Huffaker, D. Clark, and k. claffy, bdrmap: Inference of Borders Between IP Networks, Proc. ACM/SIGCOMM Internet Measurement Conference 2016.
R. Govindan and H. Tangmunarunkit, Heuristics for Internet Map Discovery, Proc. IEEE INFOCOM 2000.
N. Spring, R. Mahajan, and D. Wetherall, Measuring ISP topologies with Rocketfuel, Proc. ACM SIGCOMM 2002.
B. Donnet, P. Raoult, T. Friedman, and M. Crovella, Efficient algorithms for large-scale topology discovery, Proc. ACM SIGMETRICS 2005.
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.
A. Bender, R. Sherwood, and N. Spring, Fixing Ally's growing pains with velocity modeling, Proc. ACM/SIGCOMM Internet Measurement Conference 2008.
M. Luckie, Scamper: a Scalable and Extensible Packet Prober for Active Measurement of the Internet, Proc. ACM/SIGCOMM Internet Measurement Conference 2010.
R. Beverly, W. Brinkmeyer, M. Luckie, and J.P. Rohrer, IPv6 Alias Resolution via Induced Fragmentation, Proc. Passive and Active Measurement Conference 2013.
M. Luckie, R. Beverly, W. Brinkmeyer, and k claffy, Speedtrap: Internet-scale IPv6 Alias Resolution, Proc. ACM/SIGCOMM Internet Measurement Conference 2013.
M. Luckie, B. Huffaker, A. Dhamdhere, V. Giotsas, and k claffy, AS Relationships, Customer Cones, and Validation, Proc. ACM/SIGCOMM Internet Measurement Conference 2013.
sc_bdrmap
was written by Matthew Luckie
<mjl@luckie.org.nz>.
September 24, 2019 | Debian |