[Feature Request] Allow Outgoing Traffic via Pangolin Tunnel (VPN-like)

[kielerdotdev]

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]

Would be awesome ngl

[lakemike]

I would support this too.
(Q: Could this already be done with wireguard connecting to pangolin?)

[kielerdotdev]

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]

Moving this to a discussion to track. Interesting idea but might be covered with some upcoming stuff with clients.

[w4tzmann]

It would be a really nice feature. I would need it for my mailserver:

As far as I can see, the client needs a remote site to terminate. For my purpose, however, the VPN would have to terminate on the Pangolin host.

[MartinCanto]

Is this possible by putting gerbil on the host network in docker maybe?

[Mannshoch]

I would say my idea https://github.com/orgs/fosrl/discussions/1324 is similar.