[GH-ISSUE #640] Proxy (TS_DEST_IP feature equivalent) #1159

Open
opened 2026-08-05 00:41:23 -04:00 by saavagebueno · 5 comments
Owner

Originally created by @gdelbergue on GitHub (Dec 31, 2022).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/640

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 @gdelbergue on GitHub (Dec 31, 2022). Original GitHub issue: https://github.com/netbirdio/netbird/issues/640 **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 2026-08-05 00:41:23 -04: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?

<!-- gh-comment-id:2813259204 --> @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.

<!-- gh-comment-id:2864524343 --> @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.
Author
Owner

@FoxxMD commented on GitHub (Dec 12, 2025):

Also hoping to see this feature. I want to be able to proxy a netbird IP to a reverse proxy in a private docker network. With TS_DEST_IP like functionality I could do this by creating a new netbird peer from a netbird docker container in the same private network.

Using netbird Networks is not an option because I don't want to refer to the reverse proxy's private IP address. It may change if the stack is redeployed. I also have router-level static routing already configured to route netbird's subnet range through a routing peer so being able to re-use another ip in that range means i don't need to do any additional static routes.

<!-- gh-comment-id:3647913015 --> @FoxxMD commented on GitHub (Dec 12, 2025): Also hoping to see this feature. I want to be able to proxy a netbird IP to a reverse proxy in a private docker network. With TS_DEST_IP like functionality I could do this by creating a new netbird peer from a netbird docker container in the same private network. Using netbird Networks is not an option because I don't want to refer to the reverse proxy's private IP address. It may change if the stack is redeployed. I also have router-level static routing already configured to route netbird's subnet range through a routing peer so being able to re-use another ip in that range means i don't need to do any additional static routes.
Author
Owner

@Cyberbeni commented on GitHub (Feb 7, 2026):

In my case, I am using the rootless docker image with network_mode: host to be able to access services running on the docker host machine. However this also gives access to other parts of my network. I would like to be able to add

extra_hosts:
  - 'host.docker.internal:host-gateway'

to my docker-compose.yaml and set "TS_DEST_IP" to host.docker.internal, so that netbird only has access to the machine I want it to access.

<!-- gh-comment-id:3864366562 --> @Cyberbeni commented on GitHub (Feb 7, 2026): In my case, I am using the rootless docker image with `network_mode: host` to be able to access services running on the docker host machine. However this also gives access to other parts of my network. I would like to be able to add ```yaml extra_hosts: - 'host.docker.internal:host-gateway' ``` to my docker-compose.yaml and set "TS_DEST_IP" to host.docker.internal, so that netbird only has access to the machine I want it to access.
Author
Owner

@Wouter0100 commented on GitHub (Mar 3, 2026):

I've implemented this feature-ish myself in another Golang app with the client embed, see here.

<!-- gh-comment-id:3994174881 --> @Wouter0100 commented on GitHub (Mar 3, 2026): I've implemented this feature-ish myself in another Golang app with the client embed, see [here](https://github.com/Wouter0100/netbird-forwarder).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#1159