Pantrace converts between traceroute formats, in the same way as Pandoc converts between document formats.
Each format needs to implement only two conversions: to and from the internal format.
cargo install pantrace && pantrace --helpdocker run ghcr.io/dioptra-io/pantrace:main --helpnix run github:dioptra-io/pantrace -- --help# Fetch traceroute results from the RIPE Atlas API
curl -L -o example.ndjson \
"https://atlas.ripe.net/api/v2/measurements/23119199/results/?start=1625097600&stop=1625788799&format=txt&probe_ids=6479"
# Convert from the standard input to the standard output
cat example.ndjson | pantrace --standalone --from atlas --to scamper-trace-warts > example.warts
# Convert from a file to a file
pantrace --standalone --from atlas --to scamper-trace-warts --input example.ndjson --output example.wartsatlas: RIPE Atlas JSONL (read/write)flat: JSONL with one document per reply (write-only)internal: Pantrace internal format (read/write)iris: Iris JSONL format (read/write)scamper-trace-warts: Scamper traceroute in warts format (read/write)
To add a new CustomFormat to the pantrace CLI (main.rs), two structures must be implemented:
CustomTracerouteReaderwhich implements theIterator<Item = Result<Traceroute>>trait.CustomTracerouteWriterwhich implements theTracerouteWritertrait, and in particular thefn write_traceroute(&mut self, traceroute: &Traceroute) -> Result<()>function whereTracerouteis pantrace's internal traceroute format.
The conversion between CustomFormat and Traceroute can be implemented in any way, but the current formats are
implemented as follows:
CustomFormattoTracerouteconversion in ato_internalmodule:impl From<CustomFormat> for Traceroute { ... }
CustomFormatfromTracerouteconversion in afrom_internalmoduleimpl From<Traceroute> for CustomFormat { ... }- or
impl From<Traceroute> for Vec<CustomFormat> { ... }ifCustomFormatis a single path traceroute format