Actions
Feature #16563
open
Remove TCP flags option from firewall rule when the protocol is not TCP
Status:
New
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Description
When creating a firewall rule with Protocol set to "any", I attempted to configure TCP Flags: any flags under Advanced Options to allow asymmetric traffic. However, upon inspecting /tmp/rules.debug, I noticed the flags were not actually applied to the generated rule.
Suggestion: To prevent configuration errors, the TCP Flags option should be hidden or disabled from the GUI when the selected protocol does not support them.
No data to display
Actions