HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
grigio
network-monitor
Rust2025–2025
grigio / network-monitor

network-monitor

A real-time network connection monitoring tool built with Rust and GTK4, displaying active connections with live I/O statistics in a modern graphical interface.

4Distinct people
4Mentions
0Explicit recommenders
325GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A real-time network connection monitoring tool built with Rust and GTK4, displaying active connections with live I/O statistics in a modern graphical interface.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval4 dated mentions

Observed mentions: 2025-11-24 09:30:40 UTC to 2025-11-30 03:10:11 UTC.

0122025-11-24 06:00:00 UTC to 2025-11-24 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsNov 24, 06:002025-11-24 12:00:00 UTC to 2025-11-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-24 18:00:00 UTC to 2025-11-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-25 00:00:00 UTC to 2025-11-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-25 06:00:00 UTC to 2025-11-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-25 12:00:00 UTC to 2025-11-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-25 18:00:00 UTC to 2025-11-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-26 00:00:00 UTC to 2025-11-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-26 06:00:00 UTC to 2025-11-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-26 12:00:00 UTC to 2025-11-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-26 18:00:00 UTC to 2025-11-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-27 00:00:00 UTC to 2025-11-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 27, 00:002025-11-27 06:00:00 UTC to 2025-11-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-27 12:00:00 UTC to 2025-11-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-27 18:00:00 UTC to 2025-11-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-28 00:00:00 UTC to 2025-11-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-28 06:00:00 UTC to 2025-11-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-28 12:00:00 UTC to 2025-11-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-28 18:00:00 UTC to 2025-11-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-29 00:00:00 UTC to 2025-11-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-29 06:00:00 UTC to 2025-11-29 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-29 12:00:00 UTC to 2025-11-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-29 18:00:00 UTC to 2025-11-30 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-11-30 00:00:00 UTC to 2025-11-30 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 30, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 24, 06:002025-11-24 06:00:00 UTC2025-11-24 12:00:00 UTC110
Nov 24, 12:002025-11-24 12:00:00 UTC2025-11-24 18:00:00 UTC000
Nov 24, 18:002025-11-24 18:00:00 UTC2025-11-25 00:00:00 UTC000
Nov 25, 00:002025-11-25 00:00:00 UTC2025-11-25 06:00:00 UTC000
Nov 25, 06:002025-11-25 06:00:00 UTC2025-11-25 12:00:00 UTC000
Nov 25, 12:002025-11-25 12:00:00 UTC2025-11-25 18:00:00 UTC000
Nov 25, 18:002025-11-25 18:00:00 UTC2025-11-26 00:00:00 UTC000
Nov 26, 00:002025-11-26 00:00:00 UTC2025-11-26 06:00:00 UTC000
Nov 26, 06:002025-11-26 06:00:00 UTC2025-11-26 12:00:00 UTC000
Nov 26, 12:002025-11-26 12:00:00 UTC2025-11-26 18:00:00 UTC000
Nov 26, 18:002025-11-26 18:00:00 UTC2025-11-27 00:00:00 UTC000
Nov 27, 00:002025-11-27 00:00:00 UTC2025-11-27 06:00:00 UTC000
Nov 27, 06:002025-11-27 06:00:00 UTC2025-11-27 12:00:00 UTC000
Nov 27, 12:002025-11-27 12:00:00 UTC2025-11-27 18:00:00 UTC000
Nov 27, 18:002025-11-27 18:00:00 UTC2025-11-28 00:00:00 UTC000
Nov 28, 00:002025-11-28 00:00:00 UTC2025-11-28 06:00:00 UTC000
Nov 28, 06:002025-11-28 06:00:00 UTC2025-11-28 12:00:00 UTC000
Nov 28, 12:002025-11-28 12:00:00 UTC2025-11-28 18:00:00 UTC000
Nov 28, 18:002025-11-28 18:00:00 UTC2025-11-29 00:00:00 UTC000
Nov 29, 00:002025-11-29 00:00:00 UTC2025-11-29 06:00:00 UTC000
Nov 29, 06:002025-11-29 06:00:00 UTC2025-11-29 12:00:00 UTC000
Nov 29, 12:002025-11-29 12:00:00 UTC2025-11-29 18:00:00 UTC000
Nov 29, 18:002025-11-29 18:00:00 UTC2025-11-30 00:00:00 UTC202
Nov 30, 00:002025-11-30 00:00:00 UTC2025-11-30 06:00:00 UTC101

What Hacker News says

4 sources
I came to this conclusion as well. The README gives off some vibes but the sheer volume and writing style of the code comments is what really sells it for me. For example: https://github.com/grigio/network-monitor/blob/9dc470553bfdd... // Enhanced styling with column-specific classes and alignment This sort of marketing-speak isn't what people typically put in their code, LLMs love buzzwords. It's not just this, it's everything, but hopefully you get what I mean.
In Show HN: Network Monitor – a GUI to spot anomalous connections on your Linux
I see that you're parsing `ss` output in 'src/services/network.rs' (L22-L31) [1]. I find this to be a rather shaky foundation as any future drift or deviation in the `ss` utility's output could potentially yield unforeseen consequences. I'm vaguely aware that there are crates available in the Rust ecosystem for interrogating and manipulating sockets much more directly as well as high level abstractions for all things netlink (read: AF_NETLINK). Is wielding Rust's socket/netlink libraries unsuitable in some way, or was it merely deemed out of the design scope? Very cool project, please keep going! [1] https://github.com/grigio/network-monitor/blob/master/src/se...
In Show HN: Network Monitor – a GUI to spot anomalous connections on your Linux
Cool project, I wish we had more GUIs for these OS functions. How was your experience with GTK4 and Rust? And it's a bit sad that in the year of our lord 2025, the best way to get such fundamental information is by using regexes to parse a table[1], generated by a 6000-line C program[2], which is verified by (I hope I'm wrong!) a tiny test suite[3]. OSQuery[4] is also pretty cool, but it builds upon this fragile stack. That's something I miss from Windows, at least PowerShell has built-in commands that give you structured output. [1] https://github.com/grigio/network-monitor/blob/9dc470553bfdd... [2] https://github.com/iproute2/iproute2/blob/main/misc/ss.c [3] https://github.com/iproute2/iproute2/blob/main/testsuite/tes... [4] https://osquery.io/
In Show HN: Network Monitor – a GUI to spot anomalous connections on your Linux

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.