Wireguard on Thaddeus Koenig

09AUG2026 - Using travel routers the hard way.

Sun, 09 Aug 2026 15:50:00 -0500

01. Intro

When I travel, I have a few technology essentials that I like to bring along to include 1) travel router 2) streaming device 3) laptop. Im more likely to forget my toothbrush than I am these things and theyre going to be the focal point of this post. I like to bring a travel router for a few different reasons. The primary reason is that I dont trust any shared network so I would like to ensure there is some kind of VPN, either back to my house or to a VPN provider of my choosing. Next is that the devices I bring along with me have the travel router login pre-programmed, so once the router is plugged in they’ll auto-connect. Lastly I can continue to use my DNS ad blocking and it just helps me get around any weird network restrictions imposed wherever I am, whether thats having to pay per-device in the captive portal, or blocking websites that I like to go to. I will admit that the way I wanted it set up is very particilar, but for documentation purposed this is what I have going for my situation.

Exposing Services Behind a Firewall

Thu, 23 Nov 2023 12:00:00 -0500

Synopsis

Sometimes you may find yourself in a situation in which you would like to host a service but sometimes you’re stuck behind a double NAT, or even just a firewall in which you do not control all of the rules for. Here I’m going to show you how to use Wireguard VPN to finagle around this issue and simply give your private server a public IP address. Important note: in order for this to work, you will need a publicly accessible VPS, preferably with a static IP address, i would recommend either AWS Lighsail or Linode as they are both cost-effective options with their cheapest tiers being bout $3.50/mo and $5/mo respectively (I like Linode’s speed more, they aren’t paying me to say this although I wish they were).

Wireguard DNS issues with Debian

Thu, 23 Nov 2023 00:00:00 -0500

When utilizing debian based distros, I’ve run into this issue a lot when I’m trying to use wireguard and specify DNS settings:

/usr/bin/wg-quick: line 31: resolvconf: command not found

A lot of this is because of systemd has its own resolvconf so you can simply make a symlink to get wireguard running normally:

sudo ln -s /usr/bin/resolvectl /usr/local/bin/resolvconf