[GH-ISSUE #5643] Allow exposing localhost-bound services in the mesh network #11579

Open
opened 2026-08-05 01:30:05 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @danielniccoli on GitHub (Mar 20, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5643

Is your feature request related to a problem? Please describe.
I have a VPS which I deploy and manage by using Ansible.
The VPS hosts some services and the services must not bind to 0.0.0.0.
The services must be available in the NetBird mesh network.

At the time of the deployment, the NetBird agent is not yet installed and not connected.
Therefore it is not possible to bind the services to the non-existing NetBird interface.

Also, if for any reason the NetBird agent is disconnected the interface ceases to exist on the VPS.

That makes it extremely difficult and complex to make services available in the NetBird mesh network by IaC e.g., Ansible.

Describe the solution you'd like
I propose to add a feature that makes it possible to make a service available in the mesh network, that is bound to localhost (127.0.0.1/[::1]).

That way I can configure and serve the services reliably and independently of NetBird, and make them available at any time without changing the configuration of the services.

Describe alternatives you've considered
Have not found any.

Additional context

Originally created by @danielniccoli on GitHub (Mar 20, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5643 **Is your feature request related to a problem? Please describe.** I have a VPS which I deploy and manage by using Ansible. The VPS hosts some services and the services must not bind to 0.0.0.0. The services must be available in the NetBird mesh network. At the time of the deployment, the NetBird agent is not yet installed and not connected. Therefore it is not possible to bind the services to the non-existing NetBird interface. Also, if for any reason the NetBird agent is disconnected the interface ceases to exist on the VPS. That makes it extremely difficult and complex to make services available in the NetBird mesh network by IaC e.g., Ansible. **Describe the solution you'd like** I propose to add a feature that makes it possible to make a service available in the mesh network, that is bound to localhost (127.0.0.1/[::1]). That way I can configure and serve the services reliably and independently of NetBird, and make them available at any time without changing the configuration of the services. **Describe alternatives you've considered** Have not found any. **Additional context** -
saavagebueno added the feature-request label 2026-08-05 01:30:05 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11579