Inbound tunnels / Service mesh #1403

Closed
opened 2026-04-05 19:24:07 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @3nprob on 6/5/2025

Currently, the tunnels are unidirectional: Resources can be added to (newt or wireguard) Sites and exposed via the public Traefik reverse-proxy but as far as I can see no way for Sites to access other Sites via the Pangolin network.

We would like to have Sites able to securely access select Resources at other select Sites over the internal Wireguard network instead of having to go via the public network and the Traefik gateway.

Use-cases are for internal service-to-service access.

This would make it possible to use Pangolin like a service mesh.

One way I imagine this could be implemented would be adding configuration to newt such that it can open ports listening on localhost which would be proxied to a corresponding Resource.

Related:

*Originally created by @3nprob on 6/5/2025* Currently, the tunnels are unidirectional: Resources can be added to (newt or wireguard) Sites and exposed via the public Traefik reverse-proxy but as far as I can see no way for Sites to access other Sites via the Pangolin network. We would like to have Sites able to securely access select Resources at other select Sites over the internal Wireguard network instead of having to go via the public network and the Traefik gateway. Use-cases are for internal service-to-service access. This would make it possible to use Pangolin like a service mesh. One way I imagine this could be implemented would be adding configuration to newt such that it can open ports listening on `localhost` which would be proxied to a corresponding Resource. Related: - #771
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1403