Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Forward Rules Between the Same Zone or Any Zone #989

Open
cotosso opened this issue Dec 20, 2024 · 0 comments
Open

Allow Forward Rules Between the Same Zone or Any Zone #989

cotosso opened this issue Dec 20, 2024 · 0 comments
Assignees

Comments

@cotosso
Copy link
Contributor

cotosso commented Dec 20, 2024

Description:
In the current implementation of the forward rules, it is not possible to create rules where the source and destination are within the same zone, a specific zone, or the "any" option. This limitation results in several practical issues and inefficiencies.

Examples:

  • Rules Between Two LAN Zones:

It is currently impossible to create a rule using two LAN zones. For instance, if I have multiple LAN interfaces (each with its own CIDR), I am forced to specify one zone as LAN and the other as ANY.

  • Rules Using "Any" for Both Source and Destination:

If I want to block all traffic between zones and allow specific traffic only on certain ports using host sets, I am required to create multiple rules instead of a single, comprehensive rule.
On NethSecurity 8, the "any" option operates only within the forward context. As a result, it cannot block access to the firewall itself.

Proposed Solution:
Relax form validator to:

  • Allow the creation of forward rules where the source and destination are the same zone.
  • Enable the use of the "any" option for both source and destination in forward rules.
@cotosso cotosso converted this from a draft issue Dec 20, 2024
@cotosso cotosso added this to the NethSecurity 8.5 milestone Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ToDo 🕐
Development

No branches or pull requests

2 participants