You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I appreciate the work you're doing to simplify secure networking. While setting up access control, I realized that NetBird currently supports only allow policies but lacks a way to explicitly deny traffic.
Right now, if I need to block a specific IP (e.g., 10.4.0.36) while allowing 10.4.0.0/24, I have to create complex allow lists that manually exclude that IP. This is inefficient and difficult to manage at scale.
Feature Request:
Support Explicit Deny Policies
Ability to create policies that block traffic to/from specific IPs, subnets, or groups.
Would simplify security management instead of relying solely on allow rules.
Stateful Firewall Capabilities (I heard this is planned 👀)
Ability to filter and control inbound/outbound traffic dynamically.
Example: Restrict access based on connection state (e.g., allow established connections but block new ones).
This would make NetBird much more powerful for fine-grained security controls.
The text was updated successfully, but these errors were encountered:
Hey NetBird Team,
I appreciate the work you're doing to simplify secure networking. While setting up access control, I realized that NetBird currently supports only allow policies but lacks a way to explicitly deny traffic.
Right now, if I need to block a specific IP (e.g., 10.4.0.36) while allowing 10.4.0.0/24, I have to create complex allow lists that manually exclude that IP. This is inefficient and difficult to manage at scale.
Feature Request:
Support Explicit Deny Policies
Ability to create policies that block traffic to/from specific IPs, subnets, or groups.
Would simplify security management instead of relying solely on allow rules.
Stateful Firewall Capabilities (I heard this is planned 👀)
Ability to filter and control inbound/outbound traffic dynamically.
Example: Restrict access based on connection state (e.g., allow established connections but block new ones).
This would make NetBird much more powerful for fine-grained security controls.
The text was updated successfully, but these errors were encountered: