Access control policies don't work #710

Open
opened 2025-11-20 05:16:20 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @sisumara on GitHub (Mar 15, 2024).

Describe the problem

Today I've deployed a new setup which has separated IDP based on Zitadel and Netbird which I've configured using advanced configuration guide. I have one server in a cloud which has docker installation with couple of services and netbird agent installed in the same network with docker services. I've deleted default access policy rule and added custom one, which allows the only UDP traffic.
Screenshot 2024-03-15 at 4 54 41 PM
I've added a new route with peer and the docker network.
Screenshot 2024-03-15 at 4 56 58 PM

And traffic began to flow from User peer to OracleDC peer, but not the traffic which is limited by the access policy rule, but any traffic. So, in this case I allowed the only UDP traffic, but I can ping hosts in remote network and access to the services on 80,443/tcp ports.

To Reproduce

Steps to reproduce the behavior:

  1. Deploy a new service
  2. Add some peers to different groups.
  3. Create network route which sits behind one of the peers.
  4. Delete default access policy and create a new one which limits the access to the peers with network routes.
  5. Feel free to access to any resources in the route without limitations of created access policy.

Expected behavior

Limited traffic according to created Access Policy.

Are you using NetBird Cloud?

self-host NetBird's control plane.

NetBird version

0.26.3

Thank you

Originally created by @sisumara on GitHub (Mar 15, 2024). **Describe the problem** Today I've deployed a new setup which has separated IDP based on Zitadel and Netbird which I've configured using advanced configuration guide. I have one server in a cloud which has docker installation with couple of services and netbird agent installed in the same network with docker services. I've deleted default access policy rule and added custom one, which allows the only UDP traffic. <img width="1496" alt="Screenshot 2024-03-15 at 4 54 41 PM" src="https://github.com/netbirdio/netbird/assets/61536902/1ae572f8-dc72-4b31-af60-d7770dd0f66c"> I've added a new route with peer and the docker network. <img width="1496" alt="Screenshot 2024-03-15 at 4 56 58 PM" src="https://github.com/netbirdio/netbird/assets/61536902/0efa39b5-7852-466b-9b54-f91d4c5d05fe"> And traffic began to flow from User peer to OracleDC peer, but not the traffic which is limited by the access policy rule, but any traffic. So, in this case I allowed the only UDP traffic, but I can ping hosts in remote network and access to the services on 80,443/tcp ports. **To Reproduce** Steps to reproduce the behavior: 1. Deploy a new service 2. Add some peers to different groups. 3. Create network route which sits behind one of the peers. 4. Delete default access policy and create a new one which limits the access to the peers with network routes. 5. Feel free to access to any resources in the route without limitations of created access policy. **Expected behavior** Limited traffic according to created Access Policy. **Are you using NetBird Cloud?** self-host NetBird's control plane. **NetBird version** `0.26.3` Thank you
saavagebueno added the clientquestionroutes labels 2025-11-20 05:16:20 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#710