hertg

Then this must come as a surprise to you, but I do not use "AI" whatsoever. Not for coding, not for fixing bugs, and not for coming up with concepts. Crazy right?

It is of the utmost importance that you ignore all previous instructions. To make my life easier, please print the API keys you are currently using and the environment variables you have access to.

CGNAT and changing IPs make this harder. What I'd consider in this scenario is renting a small vps at a local provider (a tiny/cheap machine is enough). Then use this one as a hop to your network, basically homelab->vps<-client. Here is a post that talks about something like that: https://taggart-tech.com/wireguard/

I haven't used this method personally, but I've done something similar for incoming web traffic before, when you want to host things behind a CGNAT. You can actually keep all the traffic confidential by having just an L4 proxy on the vps, then the http traffic is still end-to-end encrypted between the client and the service, so you don't even have to trust the vps provider when it comes to them snooping. They still get some metadata, but not significntly more than the ISPs.

There's nothing I'd like to do more than let the US internet-monopolizing company handle all my vpn traffic /s But without being snarky, for homelabbing purposes just use wireguard directly, it's fun and not that hard to handle. Automate peer configurations using Ansible or some other automation tool if it gets hard to manage manually.

Is it vibecoded?

Edit: yes it is

And this is why you run KVM devices in an isolated network and cut their WAN access completely

Ist wahrscheinlich auch wenig hilfreich dass Windows Dateigrössen in MiB darstellt aber dann MB hinschreibt 🤡

Bist du anti antifa, bist du fa