How dioptra-io/voyage works
High-Level Components
• User Interface (CLI)
• Configuration & Builder
• Probing Engine
• Sender (crafts and transmits packets via libpcap)
• Receiver (captures replies via libpcap)
• Algorithms
• Diamond Miner (probe scheduling, ‘sequential_mapper’, ‘probe_generator’, statistical estimation)
• Classic Traceroute (fallback/simple path tracing)
• Data Aggregation & Link Discovery
• Output Formatter
• Atlas, Iris, flat, scamper, internal, quiet
• Logging & Observability
• External Dependencies
• libpcap
• stirling_numbers crate (for estimator)
• env_logger
Relationships & Data Flows
• CLI parses arguments → populates a PantraceBuilder / config struct in pantrace_builder.rs
• Builder → instantiates Probing Engine
• Sender and Receiver run concurrently (threads/tasks)
• Sender uses probe.rs to generate packets
• Receiver in receiver.rs uses libpcap to listen for ICMP/UDP replies
• Probing Engine ↔ Algorithm modules
• Diamond Miner sub‐modules (in src/algorithms/diamond_miner/*) coordinate rounds, TTL ranges, confidence estimation
• Utilities (utils.rs, stopping_point.rs) support convergence checks
• Classic traceroute path logic in classic_traceroute.rs
• Captured probe results flow into link analysis (links.rs), building a graph of hops/interfaces
• Aggregated data passed to Output Formatter (in src/lib.rs or main.rs), which serializes into the chosen format
• Logging calls interwoven across modules via env_logger
Architectural Patterns & Principles
• Builder Pattern: PantraceBuilder centralizes configuration
• Modularization: Separate crates/modules for algorithms, utils, link handling, I/O
• Pipeline/Producer-Consumer: Sender and Receiver communicate via channels or shared structs
• Pluggable Output Formats: Strategy pattern for serialization
Technologies & Frameworks
• Rust/Cargo crate layout
• libpcap FFI binding (via pantrace or similar)
• stirling_numbers crate for statistical computations
• env_logger for log levels