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"
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"
I would support this too.
(Q: Could this already be done with wireguard connecting to pangolin?)
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
@kielerdotdev commented on GitHub (Jun 9, 2025):
> I would support this too.
> (Q: Could this already be done with wireguard connecting to pangolin?)
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.
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.