u/mplaczek99 — reddlx

Looking for contributors for Network Doctor, 29 open issues to work on

I've been continuing to build Network Doctor, an open-source cross-platform network diagnostic CLI written in Go.

GitHub: https://github.com/heymaikol/network-doctor
Website: https://networkdoctor.dev/

It checks things like DNS, TCP, TLS, HTTP, proxies, routing, encrypted DNS, and path MTU, with the goal of explaining where a connection is actually failing.

The project has gotten to the point where I'd genuinely appreciate some help.

There are 29 open issues right now, ranging from smaller bugs and test improvements to performance work and more involved networking edge cases. A lot of them came from adversarial testing and deliberately trying to break things.

I've been trying to keep the project evidence-first: reproduce the problem, prove it's real, add coverage where possible, and then fix it.

I'm still actively maintaining and working through the issues myself, but I'd love to have more people contributing. If Go, networking, testing, or just hunting down weird edge cases sounds interesting to you, take a look through the issue tracker and grab anything that catches your eye.

Even reviews, testing on different platforms, or feedback on existing issues would be genuinely useful.

u/mplaczek99 — 9 days ago

▲ 0 r/networkautomation

I posted Network Doctor here a couple months ago. Here’s what it has become.

I built Network Doctor, an open-source tool for figuring out where a network connection is actually breaking.

I just released v1.17.3 today.

A problem I keep seeing is the support-ticket loop where someone says:

“Your service doesn’t work from my office network.”

Then you spend the next several replies asking for DNS results, curl output, proxy settings, traceroutes, whether it works from a hotspot, etc.

Network Doctor tries to collect that evidence in one place. It checks things like DNS, TCP, TLS, HTTP, proxies, routing, path MTU, and other layers, then explains where the evidence points.

It can also create a sanitized support snapshot locally:

netdoc --support support.ndoc example.com

The user decides whether to send that file anywhere. Network Doctor itself does not upload it.

I’m currently testing two things:

For individuals, I’m offering the first 5 personal network diagnoses for $25. You send me the sanitized report and context, and I investigate it and send back what I think is wrong, the evidence, and what to try next.
I’m looking for a few software/support teams that regularly deal with customer networking issues and might want to try Network Doctor as part of their support workflow.

The tool itself stays free and open source under Apache-2.0.

https://networkdoctor.dev/

I’d especially be interested to hear from people who deal with the “works at home, fails at the office/VPN/corporate network” class of tickets.

reddit.com

u/mplaczek99 — 26 days ago

▲ 38 r/linuxadmin+5 crossposts

I built Network Doctor, an open-source terminal app that shows where your connection breaks

When a host is unreachable, troubleshooting usually means running ping, dig, curl, and traceroute, and others, then piecing their outputs together.

So I built Network Doctor to solve that issue!

It checks the connection in stages, and explains where the chain failed in plain English.

Check it out: https://github.com/heymaikol/network-doctor

u/mplaczek99 — 2 months ago

▲ 29 r/coolgithubprojects+1 crossposts

I Built Network Doctor (A TUI to show where network connections break)

I kept reaching for ping, dig, curl, and traceroute to answer one question: where is this connection actually failing?

So I built Network Doctor. You can select a row to see the evidence or run the relevant platform tool. It also produces stable JSON for scripts too.

It is Apache-2.0, written in Go with Bubble Tea, and runs on Linux, macOS, and Windows (and others probably (did not test that))

GitHub: https://github.com/heymaikol/network-doctor

I would especially value reports of real networks it diagnoses incorrectly or incompletely.

u/mplaczek99 — 3 months ago

▲ 5 r/hyprland+1 crossposts

I made hstui, a TUI for controlling hyprsunset

Hey everyone,

I made hstui, a simple TUI for controlling hyprsunset.

Instead of typing hyprctl commands every time, hstui lets you customize profiles, and even save the configuration from a small TUI, and other things too.

https://preview.redd.it/avkscrva5b9h1.png?width=447&format=png&auto=webp&s=03b5cee0754939fe4884755634afd8e940d212b2

Repo:

https://github.com/mplaczek99/hstui

I made this for my own Hyprland setup, but I thought others might find it useful. Feedback is always welcome, especially on what features would make it better.

It's on the AUR:

https://aur.archlinux.org/packages/hstui

reddit.com

u/mplaczek99 — 4 months ago