[GH-ISSUE #4005] Resource unable to access resources on Netbird network #8454

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

Originally created by @sahps on GitHub (Jun 18, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4005

This may or may not be a bug, but I'm struggling to get something working.

Details of the systems
HPVNB01
Netbird management, signal, relay, coturn server
Hosted in Azure
No access to any other network, entirely seperate
Has netbird client installed

HPVNB02
Netbird client
Serves as the entry point to the rest of the network.
The plan is to not install netbird on every server, and instead route out of this node

HPVDOCK01
Docker container host

Groups

System Group Type
HPVDOCK01 Zabbix Server Resource
HPVNB01 Linux Servers Peer

Network
Image

The internal on-premise network has routes configured on the firewall to correctly pass traffic destined for netbird clients to HPVNB02.

Netbird Resource
Image

Policy
There is a policy to allow Zabbix Server access to Linux Servers on tcp/10050
Image

Problem
I need HPVDOCK01 to access HPVNB01 on its LAN IP.
So that is: HPVDOCK01 > Router > HPVNB02 > Netbird > HPVNB01
However the above policy isn't correct as traffic stops on HPVNB02 and doesn't get passed onto the wt0 interface.
If I create a temporary new policy for All <> All, the connectivity works.

So the question is, how do I create a policy to allow an off-network resource to access the LAN IP of an on-network peer?

Originally created by @sahps on GitHub (Jun 18, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4005 This may or may not be a bug, but I'm struggling to get something working. **Details of the systems** HPVNB01 Netbird management, signal, relay, coturn server Hosted in Azure No access to any other network, entirely seperate Has netbird client installed HPVNB02 Netbird client Serves as the entry point to the rest of the network. The plan is to not install netbird on every server, and instead route out of this node HPVDOCK01 Docker container host **Groups** | System | Group | Type | |-----------|---------------|----------| | HPVDOCK01 | Zabbix Server | Resource | | HPVNB01 | Linux Servers | Peer | **Network** ![Image](https://github.com/user-attachments/assets/708b77f1-99e9-4505-bd0e-74b7e13820a9) The internal on-premise network has routes configured on the firewall to correctly pass traffic destined for netbird clients to HPVNB02. **Netbird Resource** ![Image](https://github.com/user-attachments/assets/d05e7f68-55e6-45c3-857f-1cded1e8d612) **Policy** There is a policy to allow `Zabbix Server` access to `Linux Servers` on `tcp/10050` ![Image](https://github.com/user-attachments/assets/5f4324ce-70ef-4bf4-85a2-0773c796abd5) **Problem** I need HPVDOCK01 to access HPVNB01 on its LAN IP. So that is: `HPVDOCK01 > Router > HPVNB02 > Netbird > HPVNB01` However the above policy isn't correct as traffic stops on HPVNB02 and doesn't get passed onto the wt0 interface. If I create a temporary new policy for `All <> All`, the connectivity works. So the question is, how do I create a policy to allow an off-network resource to access the LAN IP of an on-network peer?
saavagebueno added the networkingconfig-issue labels 2026-08-05 01:18:04 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#8454