mirror of
https://github.com/fosrl/pangolin.git
synced 2026-03-12 01:44:06 -05:00
Gerbil Wireguard route traffic through VPS #265
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aaronjoeldev on GitHub (Apr 24, 2025).
Hey,
I have successfully installed Pangolin on my VPS. My current goal is to be able to use my HomeLab services remotely from my iPhone. Since there is currently no Newt solution for the iPhone, I am using Wireguard. I would like to use the rules of Pangolin to whitelist the IP of the iPhone in the VPN. However, my current problem is that with the standard Wireguard config from Gerbil, the traffic is not routed via the VPS and therefore the iPhone does not receive the VPS IP.
I have tried to set allowedIPs to 0.0.0.0/0 so that all traffic goes through the VPS. However, I then no longer have an internet connection.
My approach is now to adjust this via NAT Config on the VPS. Unfortunately, all my attempts so far have been unsuccessful. Is there a specific approach to the Pangolin setup with Gerbil to achieve this?
Thanks in advance
@oschwartz10612 commented on GitHub (Apr 24, 2025):
Hi!
This is not really a prescribed use case. Gerbil is meant really to accept connections to allow Traefik to access things on the other end of the tunnel. It is not a general purpose WG server where you can connect peer to peer. The automation will not work that way.
That being said we are working on a client VPN solution that will allow you to connect back to your newt at home with wireguard. That is in progress but should be out in a couple of weeks. It might not work on mobile at first but we could look into quick solutions to that.
I think your best bet right now would be to put a wireguard server at home and use pangolin to expose the udp traffic to it so you can connect back home.
@github-actions[bot] commented on GitHub (May 9, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (May 24, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.