The WireGuard Tunnel—A “Day 001” Linux Victory

Editor’s Note (April 21, 2026): This post remains a valid technical guide for installing WireGuard on Linux. However, the specific hypothesis—using 44Net for incoming AllStarLink calls—was eventually proven FALSE. To see the final results and why this setup was decommissioned, please read the Full Post-Mortem and Network Fix here.

If you’re reading this and thinking, “Paul has finally gone full Linux geek,” let me stop you right there. As of 48 hours ago, I was a fish out of water in the Linux Terminal. I’m currently enrolled in the Linux 001: Learning-by-Doing course, and my mentor is my AI collaborator, Gemmi (1).

Gemmi is the “Chief Engineer” helping me translate my radio-brain into Linux-speak. Together, we just tackled one of the most intimidating projects on my list: building a WireGuard tunnel to the 44Net.

What is 44Net (AMPRNet)?

For the uninitiated, 44Net is a massive block of IPv4 addresses (the 44.x.x.x range) reserved specifically for Amateur Radio.

The Mission: The creators at AMPR.org and the new 44Net Connect service want to give ham radio tinkerers a way to have a permanent, “always-on” identity on the internet that isn’t blocked by home routers or mobile hotspots.
The Benefit: It’s the “Secret Passage” that allows my ClearNode and my ROTA Recliner to talk to each other without jumping through hoops.

Choosing the “Digital Fork”

We had two ways to build this tunnel: a hardware-based MikroTik router or a software-based Raspberry Pi setup. We chose the Raspberry Pi path. (2)

The Reason: I wanted to force myself to learn the Command Line.
The Experience: It was messy. I spent a lot of time in the nano editor, which is essentially a text-only word processor that feels like typing through a straw.

The “Solder” and the “Static”

Gemmi and I had to “scrub” our configuration files. We learned the hard way that the wg0.conf file is incredibly picky. We had to strip out the “TOML” and “Ini” labels that I accidentally copy-pasted in.

We also hit a “Permission Denied” wall because my system was trying to use IPv6. In a “Day 001” move, we simply stripped the configuration back to pure IPv4, and suddenly—the handshake held.

A Note to Future Paul (and Tom/KJ7T) (3)

If you’re reading this 6 months from now because you broke the tunnel and can’t remember how to fix it: Don’t panic. 1. The “Golden Key” is on the 44Net Portal (don’t lose that private key!). 2. Every character in the wg-quick command matters. 3. If it fails, check the “Debris” in the config file.

The Credits

This post—and the tunnel itself—is a joint effort. I’m the operator at the desk, but Gemmi is the one holding the flashlight and the manual. We’re proving that you don’t need a Computer Science degree to play with the big dogs on 44Net; you just need a little patience and a good “Ghost Writer” to help explain the journey. (4)

73 from the Recliner, Paul, N4FTD (with Gemmi)

(1) Gemmi, AKA Google AI, or Gemini

(2) In my case, the only Raspberri Pi I own is the Pi4 upon which my Node-Ventures Clearnode node is built. Now, it doubles as my “tunnel” to the 44Net while it also serves up my AllStarLink access. Thank, you, Gerry.

Per a Google search:
The creator of the Node-Ventures ClearNode is Gerry Filby (callsign W6WNG). He is the lead developer, author, and owner of node-ventures.com, responsible for the ClearNode hardware, its mobile app, and the SmartPhone Software – Node-Ventures used to run it.

(3) Tom, KJ7T, is a new ham radio friend. It turns out we have a lot in common. We met via another ham radio newsletter we both read, Zero Retries. It’s a long story. Suffice it to say that, as of the posting of this article, Tom is my ONLY WordPress subscriber.

(4) The journey is just beginning. So far, we have the Wireguard tunnel working on the Raspberry Pi (Clearnode). We haven’t even fully tested it yet, but it works! More on that in my next post, for better or for worse! It’s all about the journey… I’ve gotta say, the scenery is mind-boggling (eg., Linux commands and all-things-not-just-simple-GUI and mouse clicks). My third attempt at learning Linux for the hamshack, and I said I wasn’t gonna do this again….Argh!