[GH-ISSUE #3473] Restricting access to specific hosts on Networks exposed lan #7413

Closed
opened 2026-08-05 01:12:52 -04:00 by saavagebueno · 3 comments
Owner

Originally created by @BillTheGoat on GitHub (Mar 9, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3473

Originally assigned to: @nazarewk on GitHub.

I would like to restrict access to only a couple hosts on my internal lan for a specific netbird group. This lan is part of the netbird vpn via the newer Networks feature.

There does not seem to be any way to restrict access for a limited group to only a couple hosts on this network inside netbird. Is this the case?

If so, is there some way to have a group tagged with a 802.1Q vlan tag, so my lan router can deal with this, or another solution that allows my lan router to do its job without recreating groups there?

Skill level: relative beginner, homelab enthusiast.

Attempted: Searching docs, github issues + PRs, and the net for netbird restrictions to lan hosts, as well as for netbird vlan tagging. Found nothing.

Originally created by @BillTheGoat on GitHub (Mar 9, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3473 Originally assigned to: @nazarewk on GitHub. I would like to restrict access to only a couple hosts on my internal lan for a specific netbird group. This lan is part of the netbird vpn via the newer Networks feature. There does not seem to be any way to restrict access for a limited group to only a couple hosts on this network inside netbird. Is this the case? If so, is there some way to have a group tagged with a 802.1Q vlan tag, so my lan router can deal with this, or another solution that allows my lan router to do its job without recreating groups there? Skill level: relative beginner, homelab enthusiast. Attempted: Searching docs, github issues + PRs, and the net for netbird restrictions to lan hosts, as well as for netbird vlan tagging. Found nothing.
Author
Owner

@1nerdyguy commented on GitHub (Mar 10, 2025):

This is not currently a feature of netbird. When you pass a network over, you are doing just that, passing a network.

If you'd prefer to only have access to a few hosts, the recommendation would be to install the netbird client on those hosts, put them in a group, and access via the netbird hostnames/ips.

<!-- gh-comment-id:2710594734 --> @1nerdyguy commented on GitHub (Mar 10, 2025): This is not currently a feature of netbird. When you pass a network over, you are doing just that, passing a network. If you'd prefer to only have access to a few hosts, the recommendation would be to install the netbird client on those hosts, put them in a group, and access via the netbird hostnames/ips.
Author
Owner

@nazarewk commented on GitHub (Mar 13, 2025):

You could create:

  1. Network
  2. separate Resource on /32 (single ip address) for every host you want to expose to Netbird
    • assign them a single group
  3. be sure to assign Routing Peers to the network
  4. create Access Control Policy allowing access from your limited group to a single group
<!-- gh-comment-id:2720694130 --> @nazarewk commented on GitHub (Mar 13, 2025): You could create: 1. `Network` 2. separate `Resource` on `/32` (single ip address) for every host you want to expose to Netbird - assign them a _single group_ 3. be sure to assign Routing Peers to the network 4. create Access Control Policy allowing access from your _limited group_ to a _single group_
Author
Owner

@BillTheGoat commented on GitHub (Mar 28, 2025):

You could create:

1. `Network`

2. separate `Resource` on `/32` (single ip address) for every host you want to expose to Netbird
   
   * assign them a _single group_

3. be sure to assign Routing Peers to the network

4. create Access Control Policy allowing access from your _limited group_ to a _single group_

This was my planned approach although I was planning on grouping host ips to use a single /29 block. However since netbird does not work on Android and the Android app has not been updated in months, I am not going to pursue any further. Many thanks for your time.

<!-- gh-comment-id:2762155647 --> @BillTheGoat commented on GitHub (Mar 28, 2025): > You could create: > > 1. `Network` > > 2. separate `Resource` on `/32` (single ip address) for every host you want to expose to Netbird > > * assign them a _single group_ > > 3. be sure to assign Routing Peers to the network > > 4. create Access Control Policy allowing access from your _limited group_ to a _single group_ This was my planned approach although I was planning on grouping host ips to use a single /29 block. However since netbird does not work on Android and the Android app has not been updated in months, I am not going to pursue any further. Many thanks for your time.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#7413