How best to implement subnet routing? #1518

New Issue

MrUnknownDE · 2026-04-05T19:32:37+02:00

MrUnknownDE commented

2026-04-05 19:32:37 +02:00

Originally created by @NotChristianGarcia on 5/6/2025

Network:

central pangolin server or custom traefik proxy - hardware device 001
kubehost01 - hardware device 002
- kubecontainer001 - 10.10.10.100
  - newt tunneler or tailscale (for example)
  - server1 on 0.0.0.0:1111
- kubecontainer002 - 10.10.10.200
  - server2 on 0.0.0.0:2222
- kubecontainer003 - 10.10.10.300
  - server3 on 0.0.0.0:3333

Hello! Love the service. I wanted to query a developer on best practice for deployment/implementation.

With tailscale running in an example kubernetes cluster in kubecontainer001, I can run tailscale up --authkey KEY --login-server https://headscale.domain --advertise-routes=10.10.1.200/32,10.10.1.100/32.

This allows me to route/proxy to any of the 3 kube containers with only one running tunnel. For example, I could then route server3.traefik.domain -> 10.10.10.300:3333. Does this subnet routing feature exist with Pangolin? And if it does, how would it be possible to proxy servers 1-3 from one tunnel?

I believe Pangolin can work with newt and wireguard? So the feature should be possible if not already implemented via wireguard. Pangolin would need to be updated along with newt to take multiple endpoints and ips as host I think. I've only seen newt startup with one endpoint, so I'm beginner, correct me If I'm wrong. I would be interested in implementing the feature if it's not a current priority. The CLI tools and proxy would need to be made aware of these changes. Traefik is being modified via API?

Feel free to link to docs or code. I just haven't found any specific discussion on this outside of a few issues. I appreciate the time!

*Originally created by @NotChristianGarcia on 5/6/2025* **Network:** - central pangolin server or custom traefik proxy - hardware device 001 - kubehost01 - hardware device 002 - `kubecontainer001` - `10.10.10.100` - newt tunneler or tailscale (for example) - server1 on `0.0.0.0:1111` - `kubecontainer002` - `10.10.10.200` - server2 on `0.0.0.0:2222` - `kubecontainer003` - `10.10.10.300` - server3 on `0.0.0.0:3333` Hello! Love the service. I wanted to query a developer on best practice for deployment/implementation. With tailscale running in an example kubernetes cluster in `kubecontainer001`, I can run `tailscale up --authkey KEY --login-server https://headscale.domain --advertise-routes=10.10.1.200/32,10.10.1.100/32`. This allows me to route/proxy to any of the 3 kube containers with only one running tunnel. For example, I could then route `server3.traefik.domain -> 10.10.10.300:3333`. Does this subnet routing feature exist with Pangolin? And if it does, how would it be possible to proxy servers 1-3 from one tunnel? I believe Pangolin can work with newt and wireguard? So the feature should be possible if not already implemented via wireguard. Pangolin would need to be updated along with newt to take multiple endpoints and ips as host I think. I've only seen newt startup with one endpoint, so I'm beginner, correct me If I'm wrong. I would be interested in implementing the feature if it's not a current priority. The CLI tools and proxy would need to be made aware of these changes. Traefik is being modified via API? Feel free to link to docs or code. I just haven't found any specific discussion on this outside of a few issues. I appreciate the time!

MrUnknownDE closed this issue

2026-04-05 19:32:37 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1518