Trippy — Network Analysis and Diagnostics

Latest Tool Guides / Network Analysis and Diagnostics / trippy.html

A Rust-based network diagnostic tool that combines ping and traceroute into a single interactive TUI.

Basic Information

What is this program?

Trippy is a tool that merges the traditional ping and traceroute commands and displays them in a real-time Terminal User Interface (TUI). It presents latency, packet loss, and jitter for each hop along the route to the destination using colors and graphs.

Designed as a modern replacement for mtr, it supports ICMP, UDP, and TCP traces and works with both IPv4/IPv6. It provides reverse DNS lookups and ASN information by default, and if you connect a GeoIP database, hops can be displayed on a world map.

What problem does it solve?

• When communication between servers is slow or intermittent, it identifies which network segment is causing the problem.
• Allows simultaneous verification of DNS delays and routing path issues on a single screen.
• Quickly locates bottlenecks in VPN, cloud VPC, or virtual network paths.
• Used for visual comparison and analysis when the single-line output of a standard traceroute is difficult to read.

Key Features

Real-time Hop Monitoring

Displays RTT, packet loss rate, and jitter for each router (hop) along the route to the destination, updating in real time.

• Use Case: Used when you want to check if latency spikes sharply at a specific hop.
• Result Obtained: You can identify the problematic segment within seconds.
• Limitation: Some routers block ICMP responses, so intermediate hops may appear missing.

Multi-Protocol Trace

You can trace using the selected protocol (ICMP, UDP, or TCP) and also specify a port.

• Use Case: Used when tracing with TCP 443 because the firewall only blocks ICMP.
• Result Obtained: You can verify the exact path as used by the actual port.
• Limitation: TCP tracing may require root or cap_net_raw privileges.

ASN and GeoIP Display

Queries and displays the ASN (Autonomous System Number) and geographical location for each hop.

• Use Case: Used when you want to see which ISP or cloud provider's path the traffic traverses.
• Result Obtained: You can visually distinguish between CDN, backbone, and IXP segments.
• Limitation: A GeoIP database (e.g., MaxMind, IPinfo) must be downloaded separately.

11-Language TUI

The interface is translated into 11 languages, including Korean.

• Use Case: Used when viewing diagnostic results with your team in a Korean environment.
• Result Obtained: Network diagnostics can be performed without language barriers.
• Limitation: Some detailed options are displayed with their original English names.

Installation and Execution

Ubuntu / Debian (Binary Download)

Download the binary from the official GitHub release and add it to your PATH.

# Download the latest binary from the GitHub release
curl -sL https://github.com/fujiapple852/trippy/releases/latest/download/trippy-x86_64-unknown-linux-gnu.tar.gz \
  | tar xz -C /tmp
sudo mv /tmp/trippy /usr/local/bin/trip

# Or build with cargo
cargo install trippy

cargo (Rust Ecosystem)

If you have a Rust development environment, install with cargo.

cargo install trippy

# Verify installation
trip --version

macOS / Homebrew

Install easily via Homebrew.

brew install trippy

Practical Usage Examples

Basic Trace (Real-time TUI)

Check the route to the destination and hop-by-hop latency in real time.

# Basic ICMP trace (requires sudo privileges)
sudo trip example.com

# Unprivileged mode (UDP 443)
trip example.com --udp --port 443

Trace to a Specific Hop Using TCP Protocol

Check the path to an HTTPS service behind a firewall.

# Trace the path to port 443 using TCP SYN method
sudo trip -T -P 443 api.example.com

# Check RTT, loss rate, and ASN per hop in the results

Save Defaults in a Configuration File

Save frequently used options in a configuration file.

# ~/.config/trippy/trippy.toml
[default]
protocol = "icmp"
max-hops = 30
addr-family = "ipv4"

# Automatically applied when running trip example.com afterwards