We use a few cookies

Essential cookies keep the library working. With your permission, we'd also like to use analytics to see what's useful and improve the experience. Read our Privacy Policy or Cookie Policy.

Skip to main content
Home/e-Resources/Cyber Security/Yarrp'ing the Internet
Conference ProceedingsCyber Security

Yarrp'ing the Internet

Checking your access to this record.

Abstract & Overview

Obtaining a "snapshot" of the Internet topology remains an elusive task. Existing active topology discovery techniques and systems require significant probing time -- time during which the underlying network may experience transient dynamics. This work considers how active probing can gather the Internet topology in minutes rather than days. Conventional approaches to active topology mapping face two primary speed and scale impediments: i) per-trace state maintenance; and ii) a low-degree of parallelism. Based on this observation, we develop Yarrp (Yelling at Random Routers Progressively), a new traceroute technique designed for high-rate, Internet-scale probing. Yarrp is stateless, reconstituting all necessary information from ICMP replies as they arrive asynchronously. To avoid overloading routers or links with probe traffic, Yarrp randomly permutes an input IP X TTL space. We run Yarrp at 100Kpps, a rate at which the paths to all IPv4 /24's can be mapped in approximately one hour from a single vantage point. We compare Yarrp against existing systems, and present examples of topological dynamics exposed via the high sampling rates Yarrp enables.

Cite this record

Robert Beverly (2016). Yarrp'ing the Internet. Internet Measurement Conference. https://doi.org/10.1145/2987443.2987479

Copy in another style

Beverly, R. (2016). Yarrp'ing the Internet. Internet Measurement Conference. https://doi.org/10.1145/2987443.2987479
Author names are used as deposited, so check their order before you submit.

Metadata is harvested from open-access indexes and can be incomplete. Check a citation against the published version before relying on it — see our open access & attribution policy.