Proxy (TS_DEST_IP feature equivalent) #259

Open
opened 2025-11-20 05:08:42 -05:00 by saavagebueno · 2 comments
Owner

Originally created by @guyguy333 on GitHub (Dec 31, 2022).

Is your feature request related to a problem? Please describe.

Currently, we can't forward all traffic to a specific IP.

Describe the solution you'd like

I would like to be able to redirect all traffic to a specific IP so I can setup a wildcard DNS on Netbird Node and redirect all traffic to my Ingress controller (static IP).

Describe alternatives you've considered

I didn't find one.

Additional context

Originally created by @guyguy333 on GitHub (Dec 31, 2022). **Is your feature request related to a problem? Please describe.** Currently, we can't forward all traffic to a specific IP. **Describe the solution you'd like** I would like to be able to redirect all traffic to a specific IP so I can setup a wildcard DNS on Netbird Node and redirect all traffic to my Ingress controller (static IP). **Describe alternatives you've considered** I didn't find one. **Additional context**
saavagebueno added the feature-requestwaiting-feedback labels 2025-11-20 05:08:42 -05:00
Author
Owner

@nazarewk commented on GitHub (Apr 17, 2025):

@guyguy333 is it still a relevant problem for you? Is it still not covered by the latest version? Could you provide more details about what kind of traffic is not forwarded over NetBird?

@nazarewk commented on GitHub (Apr 17, 2025): @guyguy333 is it still a relevant problem for you? Is it still not covered by the latest version? Could you provide more details about what kind of traffic is not forwarded over NetBird?
Author
Owner

@Wouter0100 commented on GitHub (May 8, 2025):

@nazarewk what feature would allow us to do something like this?

I'm also eager for this feature. This would allow you to make a specific service/IP available within your Netbird network, without the possibility of IP conflicts or selecting networks in Netbird.

E.g. I could join a Docker container running Netbird to my cluster, and forward all traffic to, for example, a database server. That database server would then be available on the Netbird IP. The bonus is that we don't have IP conflicts.

An concrete IP conflict example would be a Kubernetes API server. We manage tens of Kubernetes clusters, all internally with the same Kubernetes API IP (within Kubernetes). This would allow me to expose each Kubernetes API server on its own Netbird IP.

@Wouter0100 commented on GitHub (May 8, 2025): @nazarewk what feature would allow us to do something like this? I'm also eager for this feature. This would allow you to make a specific service/IP available within your Netbird network, without the possibility of IP conflicts or selecting networks in Netbird. E.g. I could join a Docker container running Netbird to my cluster, and forward all traffic to, for example, a database server. That database server would then be available on the Netbird IP. The bonus is that we don't have IP conflicts. An concrete IP conflict example would be a Kubernetes API server. We manage tens of Kubernetes clusters, all internally with the same Kubernetes API IP (within Kubernetes). This would allow me to expose each Kubernetes API server on its own Netbird IP.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#259