Bug #8575
closed
IPv6 NPt field order bug?
100%
Description
Hoping this isn't a duplicate of 6985, but appears to be related.
Running 2.4.3_1, appears adding a new NPt creates a broken rule, which prevents loading rules with a syntax error:
There were error(s) loading the rules: /tmp/rules.debug:195: syntax error - The line in question reads [195]: binat on $HURRICANETUNNELCA inet6 from to any -> 2001:xxx:xxxx:20::/64 2018-06-14 08:57:47 2018-06-14 08:57:48
There were error(s) loading the rules: /tmp/rules.debug:195: syntax error - The line in question reads [195]: binat on $HURRICANETUNNELCA inet6 from to any -> 2001:xxx:xxxx:20::/64
Output from /tmp/rules.debug:
binat on $HURRICANETUNNELCA inet6 from to any -> 2001:xxx:xxxx:20::/64
binat on $HURRICANETUNNELCA inet6 from any to 2001:xxx:xxxx:20::/64 ->
binat on $HURRICANETUNNELWA inet6 from to any -> 2001:xxx:xxxx:20::/64
binat on $HURRICANETUNNELWA inet6 from any to 2001:xxx:xxxx:20::/64 ->
I’m guessing the “FROM” in lines 1 & 3 shouldn’t be empty. The config in the UI isn’t empty, either initially, or when I go back to edit the NPt rule.
REFERENCES:
https://forum.netgate.com/topic/131924/firewall-rules-bug/5
https://redmine.pfsense.org/issues/6985
https://redmine.pfsense.org/issues/7712
Updated by Jim Pingle over 6 years ago
- Category set to Rules / NAT
- Assignee set to Jim Pingle
- Target version set to 2.4.4
- Affected Version set to All
- Affected Architecture All added
- Affected Architecture deleted (
)
Looks like invalid input caused it, needs some validation. Commit is on its way.
Updated by Jim Pingle over 6 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset feccd385d737ffd8c61ca977ee4d3dfa23c1aadc.