How internet-equity/traceneck works
Main Components
a. Core Components:
• Network Probing System
• Speed Testing Integration
• Packet Capture System
• Configuration Management
• Data Collection & Archive
b. External Dependencies:
• NDT7 Client
• Ookla Speedtest Client
• libpcap
• TShark (optional)
Component Organization
┌─ User Interface Layer ─────────────────────┐
• Command-line Interface (main.go) │
• ┬─────────────────────────┘
• ↓
┌─ Core Services Layer ──────────────────────┐
• ┌─────────────┐ ┌──────────┐ ┌──────────┐ │
• Network │ │ Ping │ │ Config │ │
• Module │ │ Module │ │ Module │ │
• ┘ └──────────┘ └──────────┘ │
• ┬─────────────────────────┘
• ↓
┌─ Integration Layer ──────────────────────────┐
• ┌─────────────┐ ┌──────────┐ ┌──────────┐ │
• NDT7 │ │ Ookla │ │ libpcap │ │
• Client │ │ Client │ │ │ │
• ┘ └──────────┘ └──────────┘ │
• ┘
Component Relationships
a. Data Flow:
• CLI → Network Module
• Network Module ↔ Speed Test Clients
• Network Module ↔ Packet Capture
• Ping Module ↔ Network Interfaces
b. Dependencies:
• Config Module → All Components
• Archive Module → Data Collection
Specific Implementation Details
Important architectural elements:
a. Network Probing:
• ICMP/UDP ping capabilities
• TTL-based hop discovery
• Direct hop ping support
b. Speed Testing:
• NDT7 integration
• Ookla integration
• Packet capture during tests
c. Data Collection:
• Metadata gathering
• Archive creation
• Output formatting
The data collection and output options
Keep the abstraction level focused on the major components while showing the key integration points with external tools and libraries. This will help maintain clarity while providing sufficient technical detail for implementation understanding.
Remember to highlight the system's primary purpose: network bottleneck analysis in access networks, and how each component contributes to this goal.