[GH-ISSUE #1414] ACLs have no effects on Network Routes #2311

Open
opened 2026-08-05 00:46:28 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @benjvfr on GitHub (Dec 28, 2023).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1414

Describe the problem
When adding a network route with a routing peer, the ACL do not seems to apply. See below for the complete use case.
(NetBird 0.25.2)

To Reproduce
Steps to reproduce the behavior:

  1. Add a routing peer named "edge-gw" (Docker) which is placed in the DMZ of the private network. The underlying network is configured to let this routing peer being able to route to a service (my-private-service) hosted in the private network at 10.50.0.4/32 (web service on TCP 443).

  2. Tag the "edge-gw" routing peer with "Edge" tag.

  3. In "Network Routes", click "Add route" :

  • Network Identifier > my-private-service
  • Network Range > 10.50.0.4/32
  • Routing Peer > Select "edge-gw"
  • Distribution groups > "Developers"
  • Enabled > True
  • Masquerade > True
  1. In "Access Control" :
  • All rules are disabled, except for DNS forwarding (which is routed through the same "edge-gw" routing peer).
  1. On a "dev-peer" machine, which belongs to the 'Developers" group :
  • "netstat -nr" show the route 10.50.0.4/32 being distributed (which seems right)
  • curl https://my-private-service.<redacted-domain> (10.50.0.4) returns the web HTML page, which seems wrong as no ACL rules are setup to allow traffic for TCP 443 in NetBird ACL. Same for pinging 10.50.0.4.

Expected behavior
If no ACL are enabled, traffic should not be forwarded to the private network via routing peer (even if route is distributed). As no ACL route exists for "Developers > Edge" on TCP 443, traffic should be dropped. This is not the case.

Screenshots

  1. Routing peer "edge-gw" :
    Capture d’écran 2023-12-28 à 11 24 49
Capture d’écran 2023-12-28 à 11 27 03
  1. Network routes
    Capture d’écran 2023-12-28 à 11 29 45

  2. ACL
    Capture d’écran 2023-12-28 à 11 33 28

  3. Dev peer
    Capture d’écran 2023-12-28 à 11 32 52

routes curl

Is this the normal behavior ? Or I misconfigured something ?

Originally created by @benjvfr on GitHub (Dec 28, 2023). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1414 **Describe the problem** When adding a network route with a routing peer, the ACL do not seems to apply. See below for the complete use case. (NetBird 0.25.2) **To Reproduce** Steps to reproduce the behavior: 1. Add a routing peer named "edge-gw" (Docker) which is placed in the DMZ of the private network. The underlying network is configured to let this routing peer being able to route to a service (my-private-service) hosted in the private network at 10.50.0.4/32 (web service on TCP 443). 3. Tag the "edge-gw" routing peer with "Edge" tag. 4. In "Network Routes", click "Add route" : - Network Identifier > my-private-service - Network Range > 10.50.0.4/32 - Routing Peer > Select "edge-gw" - Distribution groups > "Developers" - Enabled > True - Masquerade > True 5. In "Access Control" : - All rules are disabled, except for DNS forwarding (which is routed through the same "edge-gw" routing peer). 7. On a "dev-peer" machine, which belongs to the 'Developers" group : - "netstat -nr" show the route 10.50.0.4/32 being distributed (which seems right) - **curl https://my-private-service.<redacted-domain\> (10.50.0.4) returns the web HTML page, which seems wrong as no ACL rules are setup to allow traffic for TCP 443 in NetBird ACL. Same for pinging 10.50.0.4.** **Expected behavior** If no ACL are enabled, traffic should not be forwarded to the private network via routing peer (even if route is distributed). As no ACL route exists for "Developers > Edge" on TCP 443, traffic should be dropped. This is not the case. **Screenshots** 1. Routing peer "edge-gw" : <img width="1244" alt="Capture d’écran 2023-12-28 à 11 24 49" src="https://github.com/netbirdio/netbird/assets/39627260/8c4a9f3f-db60-440c-aeed-f6bb8db52efb"> <img width="1137" alt="Capture d’écran 2023-12-28 à 11 27 03" src="https://github.com/netbirdio/netbird/assets/39627260/5272ed80-1dbf-4961-aa34-bd42d52a85e6"> 2. Network routes <img width="1220" alt="Capture d’écran 2023-12-28 à 11 29 45" src="https://github.com/netbirdio/netbird/assets/39627260/1d12ea5f-a5c0-4765-bd32-9eb4916ddc19"> 3. ACL <img width="1216" alt="Capture d’écran 2023-12-28 à 11 33 28" src="https://github.com/netbirdio/netbird/assets/39627260/9eb36880-a717-4b86-8b66-921b6c91b8df"> 4. Dev peer <img width="1237" alt="Capture d’écran 2023-12-28 à 11 32 52" src="https://github.com/netbirdio/netbird/assets/39627260/5b73132c-063a-40a2-b6b1-d4643579716a"> <img width="1396" alt="routes" src="https://github.com/netbirdio/netbird/assets/39627260/c1746315-105d-4747-af06-85369456c617"> <img width="1396" alt="curl" src="https://github.com/netbirdio/netbird/assets/39627260/e5649504-991a-4516-ad8f-bcc3b3696656"> Is this the normal behavior ? Or I misconfigured something ?
saavagebueno added the routesagent labels 2026-08-05 00:46:28 -04:00
Sign in to join this conversation.
No Label agent routes
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2311