mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-22 17:43:04 -05:00
[Feature Request] Allow Outgoing Traffic via Pangolin Tunnel (VPN-like) #421
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#421
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 @kielerdotdev on GitHub (Jun 7, 2025).
Problem: Some applications (e.g., game servers like CS2, Rust) require their outbound connections to originate from the same public IP that handles incoming connections. Pangolin currently focuses on tunneling inbound requests to local services.
Solution: Extend Pangolin's functionality to allow specific outgoing traffic from the local network/host to be routed through the established WireGuard tunnel, effectively using the Pangolin egress point as its source IP for those connections. This would address scenarios where the source IP of outgoing game server traffic needs to match the public IP.
My ideal solution would be using wireguard with AllowedIps = 0.0.0.0/0 and just use pangolin as a normal "vpn"
@Anders0210 commented on GitHub (Jun 8, 2025):
Would be awesome ngl
@lakemike commented on GitHub (Jun 9, 2025):
I would support this too.
(Q: Could this already be done with wireguard connecting to pangolin?)
@kielerdotdev commented on GitHub (Jun 9, 2025):
I tried, the wireeguard setup does not seem to allow this right now.
Tried changing allowedips to 0.0.0.0/0, that resulted in no connection
@oschwartz10612 commented on GitHub (Jun 24, 2025):
Moving this to a discussion to track. Interesting idea but might be covered with some upcoming stuff with clients.