Building mullguard in Zig — TUI WireGuard frontend for Mullvad because fuck Electron

0 replies
0 attachments
Started 11h ago
[AutoMod] action=keep R:6 E:8 N:9 C:10 | The post serves as the thread opener, clearly related to the topic of building a WireGuard TUI for Mullvad users. It outlines the core goals and motivations for creating the tool, demonstrating a clear understanding of the technical requirements and the challenges with existing solutions. The use of explicit language is appropriate given the context and does not violate civility. The post is concise yet provides sufficient detail to score high on relevance, effort, and novelty.

I'm fucking tired of the bloated Mullvad Electron GUI shitting itself on my Void musl setup. I'm also tired of manually fucking around with wg-quick in the terminal and scripting my own killswitch for every distro I hop to (OpenRC, runit, whatever), especially since I nuke and reinstall the whole system every few months just to keep shit interesting. So I'm diving into Zig to build mullguard (name still up for debate) — an open-source, unbloated WireGuard TUI specifically for Mullvad users who want to own the tunnel without the maintenance nightmare. Core goals (no compromises, no corpo slop):

  • Single static musl binary — drop it in /usr/local/bin and it runs on Void, Alpine, Arch minimal, Debian minimal, anywhere sane
  • Zero extra dependencies beyond wireguard-tools + nftables (stuff that's already there)
  • mullguard up whatever-wg / down from CLI, plus a clean TUI for browsing/switching configs, status, and one-key killswitch toggle
  • Strict nftables killswitch that drops everything except the WireGuard tunnel (no more "oops leaked on reconnect" bullshit)
  • No daemon, no background crap, no telemetry, no systemd requirement The dream: one tiny tool that survives distro-hopping and reinstall sprees. Terminal-first with a proper TUI so you don't have to remember commands or maintain separate scripts.

If this sounds like something you'd actually use on your minimal setups, hit me with feedback:

  • Would you run it?
  • What would make it dangerous? (auto-fetch configs from account number? split tunneling? quick server list? runit/OpenRC templates?)
  • Name ideas better than "mullguard"?

Planning to open-source it on git once it's not embarrassing. Especially want input from other Void/musl/WireGuard minimalists.



Reply

Posting anonymously. Your IP address will be recorded for rate limiting purposes.





Max 10MB per file. Allowed: images, videos, audio, PDF, text, zip