TGViewer
WireGuard - Reddit WireGuard - Reddit @r_wireguard · 486 subscribers
Post #9777 25
MasselGUARD - Opensource WireGuard client with automations for Windows X64/ARM64

[MasselGUARD in the Forking Fox theme](https://preview.redd.it/xt6tmfvl2uph1.png?width=1195&format=png&auto=webp&s=91b87db9f0bf3492d0d955aedb7edcbd750ca7fb)

MasselGUARD sits in the system tray and watches your WiFi connection. When you join a known network it activates the right WireGuard tunnel automatically. When you leave, or land on an unknown network, a configurable fallback fires. It also works as a clean manual WireGuard front-end. **Native x64** ***and*** **ARM64.** Fully themable and with 20+ shipped themes.

**Github:** [**https://github.com/masselink/MasselGUARD**](https://github.com/masselink/MasselGUARD)

**Download:** [**https://masselink.net/**](https://masselink.net/)

**New in version 4.0.0**

# Split tunneling (route / IP-based)



Every local tunnel's editor now has a **Split** tab with three modes:

* **Off** — route everything through the tunnel (the classic full tunnel; unchanged default).
* **Exclude these ranges** — a full tunnel *except* the destination IP ranges you list (e.g. keep your printer, LAN or a streaming service on the normal connection).
* **Only these ranges** — the opposite: only the listed ranges go through the tunnel, everything else uses your normal connection (a classic split VPN to specific subnets/services).

List the ranges one per line in **CIDR notation** (`192.168.1.0/24`) or as a single address (`10.0.0.5`); **IPv4 and IPv6** are both supported. Under the hood MasselGUARD computes the tunnel's effective routes for you (the standard WireGuard *AllowedIPs* math) — no manual route tables.

It plays correctly with the **kill switch**: in *Exclude* mode the excluded ranges are still allowed out over your normal connection instead of being blocked. Your split settings also **travel with an exported tunnel** (`.conf` / `.mgconf`) and show up in `MasselGUARDcli info`.

>**Coming later:** *per-app* split tunneling (choose by application rather than IP range) — planned for a later 4.x update.

# Also in this release



* **Cap-killed marker is now red.** When *Kill at cap* disconnects a tunnel, the 🛑 marker by its Connect button is properly coloured.
* **Usage indicator: bars or rings.** Each tunnel's data-cap usage now shows on its row as slim horizontal **bars** (day / week / month, colour-coded, with the exact breakdown on hover) — the new default. The bars now **stretch to use the available width** and **line up across every row** (connected and disconnected) so they read cleanly. Prefer the original compact **rings**? Switch it in **Settings → Appearance**.
* **Live traffic moved to the info panel.** The per-tunnel ↑/↓ figures that used to crowd each tunnel row are now a single **combined ↑/↓ total for all active tunnels**, shown (with a live status dot) in the Timeline / Data-usage panel header — hover it for the per-tunnel breakdown. The rows are cleaner and, in Timeline view, the ◀ ▶ session arrows sit just to the right of that total.
* **Heads-up when running from OneDrive.** If you launch MasselGUARD from a cloud-synced folder (OneDrive), it now warns you that **local tunnels can't start there** — the tunnel service runs as *LocalSystem*, which can't read files in your personal cloud folder (you'd otherwise get a cryptic "Element not found"). Move it to a normal local folder (e.g. `C:\MasselGUARD` or Program Files). Localised in all 12 languages; companion (WireGuard-for-Windows) tunnels are unaffected.
* **Sharper window buttons.** The minimize / maximize / close buttons in the title bar are now crisp vector icons at a uniform size.
* **New "Forking Fox" theme.** A signature theme for this release — a low-poly fox on warm ember tones (dark + light) — in the theme browser under **Settings → Appearance → Download themes…**.
* **Polish.** Wider tunnel dialogs (no more clipped *Kill at cap*), and the Theme Manager's theme list scrolls with the mouse wheel again.
* **Hide a usage ring per period.** Each period (daily / weekly / monthly) in the tunnel editor's DATA-USAGE section now has its own
More from @r_wireguard
  1. Sep 25, 2026IPSec VPN through Wireguard Hello, I would like to use an IPSec VPN through Wireguard but…
  2. Sep 24, 2026wireguard 1.1.1 for windows released what security issue did it fix? do i need to update m…
  3. Sep 22, 2026Self-Hosting Behind CGNAT https://david.alvarezrosa.com/posts/self-hosting-behind-cgnat/ h…
  4. Sep 21, 2026What is the least risky way to rotate WireGuard peer keys on devices that may stay offline…
  5. Sep 19, 2026Compromised key reverse access Title might be kinda misleading as i don't have the knowled…
  6. Sep 18, 2026Wireguard vpn handshake issues /r/VPS/comments/1wjw76k/wireguard_vpn_handshake_issues/ htt…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →