-- Leo's gemini proxy
-- Connecting to shit.cx:1965...
-- Sending request
-- Meta line: 20 text/gemini; lang=en
. * ⠈ + ⠈ + ──╕ ○ . ⠈ ⠐ ● . ╒═╕╞═╕ ╕ ╪═ * . ╘═╕│ │ │ │ .cx + . ....╘═╛╘ ╘ ╘ ╘═ ....: ⠐ . . * ⠐ .
A few months ago I switched from working mostly in a VirtualBox Linux VM to a physical server on my home network.¹ This introduced some networking problems that I didn't previously have. I need to be able to work from the office, or other places away from my home. It's easy enough to open SSH on my home router, but the problem runs deeper than that.
My work flow requires a way to connect from the server back to my laptop. I use it for sharing files, syncing my clipboard and opening files (like images) on my laptop. I've covered this setup in an earlier post if you care for the details.²
I could poke holes in firewalls wherever I go, but it's not feasible. I doubt my work would agree to this plan, for one. Instead, I setup WireGuard³. I opened a port on my firewall to allow my laptop initiate a WireGuard connection to my server. Once the tunnel is up, the client and server both get a static IP address on a new network (220.127.116.11) without any firewall restrictions. I get access to my server in exactly the same way as before.
Fortunately, my home router supports hairpin routing⁴ so I can use my public IP address to stand up the tunnel from within my home network or on the internet. This means I can use a single WireGuard configuration on my laptop that stays connected.
The content for this site is CC-BY-SA-4.0.
-- Response ended
-- Page fetched on Fri Jul 30 07:50:23 2021