Menu

1 / 3

wtfi2: Find the Hop Where Your Wi-Fi Connection Actually Dies

DEV Community: rust·kt·4 days ago
#1cSR25Ug
#devtorust#devto#dev#wtfi#exit
Reading 0:00
15s threshold

The Wi-Fi icon shows full bars. The browser says "Offline". Then I am in a terminal running ping and traceroute , trying to line the answers up in my head.

My first attempt at fixing that was wtfi , a Go CLI for macOS that printed every check as a flat list. It was still ten lines I had to correlate myself. So I rewrote it in Rust as wtfi2: it draws the connection as a chain, probes every hop at once, and answers in one line.

Source: https://github.com/kanywst/wtfi2

Install: brew install kanywst/tap/wtfi2 or cargo install wtfi2 (the command is wtfi )

Runs on macOS and Linux, no sudo

One line, then the evidence

wtfi sweeps Host, Wi-Fi, Gateway, Internet, DNS and captive portal concurrently, then walks the finished chain for the first hop that failed. Everything after that hop is collateral and does not get a verdict of its own.

A DNS-only outage, from the hidden --demo flag (a --features demo build that replays scripted sweeps on RFC 5737 addresses, so nothing here is my network).…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.