DEV Community

Cover image for Visualize Your WiFi Stability in the Linux Terminal with Wavemon
Benji377
Benji377

Posted on • Edited on

Visualize Your WiFi Stability in the Linux Terminal with Wavemon

I recently discovered a CLI gem called Wavemon, and if you are running Linux on a laptop or a device with a wireless card, you need to check this out.

We've all been there: the internet feels "slow," but you aren't sure if it's your ISP, your router, or just bad signal reception in the corner of the room. wavemon is an ncurses-based monitor that gives you a live, dashboard-style view of your wireless hardware right in the terminal.


How to Install

It is available in most standard repositories.

Debian/Ubuntu/Kali:

sudo apt install wavemon
Enter fullscreen mode Exit fullscreen mode

Arch Linux:

sudo pacman -S wavemon
Enter fullscreen mode Exit fullscreen mode

Fedora:

⚠️ Disclaimer: The official wavemon package is currently orphaned on Fedora and does not support the latest releases (e.g., Fedora 43+). There is a discussion about this on the Fedora Forums

If the standard command fails:

sudo dnf install wavemon
Enter fullscreen mode Exit fullscreen mode

You can install it via the community-maintained ntulinux COPR repository:

sudo dnf copr enable ntulinux/wavemon
sudo dnf install wavemon
Enter fullscreen mode Exit fullscreen mode

Building from Source (Any Distro):

If your package manager doesn't have it, or if you just want to compile the absolute latest release, you can build it directly from the official GitHub repository.

Finally, to run it, simply type:

sudo wavemon
Enter fullscreen mode Exit fullscreen mode

(ℹ️ Note: sudo is often required to see the scan data and sensitive details).


Understanding the Dashboard

When you launch it, you are greeted with the F1 (Info) screen. It looks like a retro sci-fi dashboard, but every number tells a story. Here is how to read the most important parts:

1. Signal Level (The big bar)

This is the most critical metric. It is measured in dBm (decibel-milliwatts).

  • The confusing part: These numbers are negative. The closer to 0, the better.
  • The Scale:
  • -30 to -50 dBm: Excellent signal. You are likely very close to the router.
  • -50 to -67 dBm: Good signal. Perfect for streaming and gaming.
  • -67 to -70 dBm: Okay. Web browsing is fine, but you might notice lag in video calls.
  • -80 dBm or lower: Bad zone. Frequent disconnects and packet loss.

2. RX vs. TX Rates

You will see lines for rx rate and tx rate.

  • RX (Receive): How fast your computer can download data from the router.
  • TX (Transmit): How fast your computer can upload data to the router.

ℹ️ Note: These are "link speeds," not your internet speed. If your RX rate is 780 Mbit/s for example, that is the theoretical speed between you and the router. If you only pay your ISP for 100 Mbit/s internet, you will still only get 100 Mbit/s, but your local file transfers (like moving files to a NAS) will be blazing fast.

3. Link Quality

This is usually a percentage or a fraction (e.g., 57/70). It calculates the signal-to-noise ratio. If this drops below 40%, you are likely experiencing interference from neighbors or microwaves.

4. The "Retry" Count

Look for the line that says retries.

  • Low number: Good.
  • High number (rapidly increasing): This means your WiFi card is shouting data at the router, but the router isn't hearing it, so it has to shout again. This usually happens in crowded WiFi areas (apartment buildings) or when you are too far away.

Suggestions:

  • F2 (Level Histogram): Press F2 to see a moving graph of your signal. Walk around your house with your laptop open to this screen. You can literally see the signal drop when you walk behind a thick concrete wall or a refrigerator.
  • F3 (Scan): Shows all other WiFi networks nearby. Great for seeing if your neighbors are clogging up your specific WiFi channel.

Summary

If you are debugging network issues or just want to feel like a hacker while checking your WiFi strength, wavemon is a must-have in your Linux toolkit.

Happy networking!


Updates

  • 23.05.2026: Thank you to @dacbarbos for informing me about the orphaned Fedora package!

Top comments (0)