Extracting Single-Path Traceroutes
In response to community feedback, we’ve developed a proof of concept tool that examines and extracts single-paths scamper‘s MDA traceroutes.
An Overview of M-Lab’s Traceroute Data
Summary
This blog post is a report on M-Lab’s traceroute data so the community can have a better understanding of what the data we make available includes.
Migration to the v2 Data Pipeline
If you typically use the measurement-lab.ndt.unified_uploads or measurement-lab.ndt.unified_downloads views, then nothing will change. We are updating the ndt5, switch, and tcpinfo schemas, removing obsolete views, and renaming some views in preparation for improving ease of use and documentation.
Accessing Traceroute Data and Format Change RFC Results
Two recent disucssions on Traceroute on our M-Lab Discuss group provided clarity on how to access Traceroute data in BigQuery, as well as solicited feedback from the community on proposed changes to the traceroute output format.
Traceroute Format Change Request for Comments (RFC)
M-Lab’s traceroute-caller (TRC) tool was designed and developed in early 2019 as a sidecar service running on M-Lab servers. Its purpose is to collect traceroute data to any remote IP address after it closes its TCP connection to an M-Lab server. TRC uses the scamper tool for running traceroutes.
New Traceroute Binary on M-Lab platform
M-Lab has always committed to provide traceroute data for the tests running on M-Lab platform. Since we launched new platform in 2019 Q4, the new traceroute binary, Scamper, replaced Paris Traceroute on all our servers. Our BigQuery table for traceroute now has unified schema to cover both the legacy Paris Traceroute test data and new Scamper data. This blog is to analyze the difference between the legacy data and new data.