https://github.com/wg-easy/wg-easy
Plus
https://github.com/qdm12/gluetun
The idea being; I can use a normal wireguard VPN from anywhere in the world to connect back to my homelab, all while being able to access stuff on my network, but also have my public IP address set by the gluetun container?
Anyone done this? Or have a docker conpose?
I followed this to access my homelab via VPN and the connect to protonvpn.
Giving me local access and public IP fro. Proton!
I tried this a while ago in combination with tailscale, exposing the VPN as an exit node. However, I found the performance to be problematic.
I am about to do the same, yet I haven’t done it. As soon as I set it up I’ll share it with you but that could take some days/ weeks whenever I have the time. I don’t expect any difficulties in that setup. To me the most difficult part is to set up wg-easy
I have something similar . I have WG on the host to access my services and gluetun in a container using openvpn for specific services.
In my case I have the host wg pass through connections to the outside via iptables rules but I’m not forwarding the connection to gluetun. I have the ip of my server as my ip.
In your case as you want a commercial vpn ip as your exit ip you would need to use iptables to pass traffic between the 2 networks .
I’m not understanding what you’re asking.
Why would you need gluetun?
So my public IP address changes. Using just wireguard makes my public IP just my home’s public IP. It would be nice to be able to make it a 2-in-1 where my public IP becomes that of a paid VPN account, based on the gluetun container
So you just want a Wireguard server at home which is connected full-time to a VPN, and then you want to port-forward from that VPN back to your home Wireguard server? Dynamic DNS for your IP seems a lot more convenient and stable.
