[GH-ISSUE #1297] Expanding Access Control rules to support CIDR notations #2167

Open
opened 2026-08-05 00:45:41 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @n5ke on GitHub (Nov 8, 2023).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1297

Hi, very nice project, thanks for making it opensource

Are there any thoughts about expanding the access control functionality to be able to include address definitions instead of just Netbird peers?

Is your feature request related to a problem? Please describe.

There are many situations where service hosts cannot or is not desirable to be joined as peers directly and would be accessed through a routing peer. Having support for Network Routes acknowledges this. Allowing to manage firewall rules between routing peers and other networks would allow for more granular control and flexibility in such scenarios.

Describe the solution you'd like

From a usability perspective I think the ideal would be to expand the notion of Groups to be able to encompass both peers and CIDR definitions, or create a new "External Resources" construct for this that can be sourced into the Access Control definitions the same way. It might also be convenient to allow defining lists of Services as Protocol/Port definitions and allow selecting these on the Access Control lists.

Describe alternatives you've considered
At the moment the only alternative way would be to either manually manage firewall rules on the routing netbird peer (probably unfeasible if there is no way of assigning fixed addresses to peers), or manually DNATing the desirable services on Netbird routing peers and control the access to them through the existing Netbird functionality -but that, aside from the lack of convenience, comes with its own issues.

Originally created by @n5ke on GitHub (Nov 8, 2023). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1297 Hi, very nice project, thanks for making it opensource Are there any thoughts about expanding the access control functionality to be able to include address definitions instead of just Netbird peers? **Is your feature request related to a problem? Please describe.** There are many situations where service hosts cannot or is not desirable to be joined as peers directly and would be accessed through a routing peer. Having support for Network Routes acknowledges this. Allowing to manage firewall rules between routing peers and other networks would allow for more granular control and flexibility in such scenarios. **Describe the solution you'd like** From a usability perspective I think the ideal would be to expand the notion of Groups to be able to encompass both peers and CIDR definitions, or create a new "External Resources" construct for this that can be sourced into the Access Control definitions the same way. It might also be convenient to allow defining lists of Services as Protocol/Port definitions and allow selecting these on the Access Control lists. **Describe alternatives you've considered** At the moment the only alternative way would be to either manually manage firewall rules on the routing netbird peer (probably unfeasible if there is no way of assigning fixed addresses to peers), or manually DNATing the desirable services on Netbird routing peers and control the access to them through the existing Netbird functionality -but that, aside from the lack of convenience, comes with its own issues.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2167