Bug #13027
closed
Input validation requires a gateway for floating ``match out`` rules
100%
Description
When implementing limiters using floating match rules, a gateway should not be necessary. Without selecting one, the following input validation message shows after clicking Save:
Please select a gateway, normally the interface selected gateway, so the limiters work correctly
It should be possible to create a floating match rule with limiters without setting a gateway.
Related issues
Updated by Marcos M about 2 years ago
This works on 22.01 with the following rule and patch:
match out on { vmx1 } inet from 192.0.2.0/28 to any ridentifier 1649027215 dnqueue( 1,2) label "USER_RULE"
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/704
This also fixes the case when trying to create a match out rule with IPv4+IPv6. Without the patch, input validation prevents the rule from being saved due to no gateway being selected, however no gateway can be selected due to the address family being IPv4+IPv6.
Updated by Jim Pingle about 2 years ago
- Status changed from New to Pull Request Review
- Target version set to CE-Next
- Plus Target Version set to 22.09
Updated by Jim Pingle about 2 years ago
- Blocked by Bug #12579: Utilize ``dnctl(8)`` to apply limiter changes without a filter reload added
Updated by Marcos M almost 2 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset 6b73b812b884cbc394137b07bab34b9a23bc66f0.
Updated by Marcos M almost 2 years ago
- Subject changed from Input validation prevents adding a floating match rule with limiters and no gateway to Input validation requires a gateway for floating ``match out`` rules
- Status changed from Feedback to Resolved
- Target version changed from CE-Next to 2.7.0
- Plus Target Version changed from 22.09 to 22.05
Works as expected. Testing details in MR.
Updated by Jim Pingle almost 2 years ago
- Category changed from Web Interface to Rules / NAT
- Assignee set to Marcos M