[GH-ISSUE #5743] [Docs] Clarify parts in Network Routes; relayed connections vs. peers themselves #11930

Open
opened 2026-08-05 01:31:41 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @IngwiePhoenix on GitHub (Mar 30, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5743

Is your feature request related to a problem? Please describe.
I currently am facing troubble understanding the documentation - in particular this one:

Within, this blurb is shown:

A network route grants access to the network behind the routing peer, not to the routing peer machine itself. If you need to reach services running on the routing peer, create a separate peer-to-peer access control policy that targets the routing peer's group as the destination.

Describe the solution you'd like
Right now, this annotation is very opaque - especially to new users. I am trying to work this out, but I found it quite confusing.

Hence, I would like a small sub-section with a short list of things to do to enable relayed peers to access VPN peers. Every other use-case is finely covered in much detail. Except... this one. It feels like a pitfall that can be avoided quite easily. :)

To be a little more precise: I am new to NetBird, have not fully gotten my mind around the singular and grouped Access Control Policies and the fact that they can be both on their own and grouped is a little all over the place - for me, anyway. Hence why I opened this ticket.

Describe alternatives you've considered
Alternatively, just make it a small separate page in the docs as an advanced topic or tutorial perhaps?

Additional context
Nothing, really. There is more context in my topic on the forum - but that does not immediately belong to this ticket.

PS.: I marked this as a feature request ticket, because I did not immediately find the documentation repository, I'd have filed it there instead. Apologies if I have simply overlooked it... Thanks!

Originally created by @IngwiePhoenix on GitHub (Mar 30, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5743 **Is your feature request related to a problem? Please describe.** I currently am facing troubble understanding the documentation - in particular this one: - https://docs.netbird.io/manage/network-routes#routing-peer Within, this blurb is shown: > A network route grants access to the network behind the routing peer, not to the routing peer machine itself. If you need to reach services running on the routing peer, create a separate peer-to-peer [access control policy](https://docs.netbird.io/manage/access-control) that targets the routing peer's group as the destination. **Describe the solution you'd like** Right now, this annotation is very opaque - especially to new users. I am [trying](https://forum.netbird.io/t/network-routing-from-homelab-to-vpn-hub-ips/661) to work this out, but I found it quite confusing. Hence, I would like a small sub-section with a short list of things to do to enable relayed peers to access VPN peers. Every other use-case is finely covered in much detail. Except... this one. It feels like a pitfall that can be avoided quite easily. :) To be a little more precise: I am new to NetBird, have not fully gotten my mind around the singular and grouped Access Control Policies and the fact that they can be both on their own and grouped is a little all over the place - for me, anyway. Hence why I opened this ticket. **Describe alternatives you've considered** Alternatively, just make it a small separate page in the docs as an advanced topic or tutorial perhaps? **Additional context** Nothing, really. There is more context in my [topic on the forum](https://forum.netbird.io/t/network-routing-from-homelab-to-vpn-hub-ips/661) - but that does not immediately belong to this ticket. PS.: I marked this as a feature request ticket, because I did not immediately find the documentation repository, I'd have filed it there instead. Apologies if I have simply overlooked it... Thanks!
saavagebueno added the feature-request label 2026-08-05 01:31:41 -04:00
Author
Owner

@mathew-uems commented on GitHub (Mar 30, 2026):

The recommended method is using Networks.
https://docs.netbird.io/manage/networks/use-cases

<!-- gh-comment-id:4159176010 --> @mathew-uems commented on GitHub (Mar 30, 2026): The recommended method is using Networks. https://docs.netbird.io/manage/networks/use-cases
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#11930