2.13-2.14 NAT, Firewall Issue
-
I installed PFsense at version 2.13 originally, and was new to it at that point.
In 2.13, when I set up NAT rules, Firewall rules were automatically created. When the NAT rules were changed, or disabled/enabled, the firewall rules were altered accordingly. Since the upgrade, if I disable or enable a NAT rules, the associated firewall rules is NOT changed. However, if I add/remove, or change any other setting in a NAT rule, the associated firewall is changed. Its just enable/disable that isn't reflected. Has anyone else noticed this? Is it a flaw in 2.14? or a bug from upgrading that would be fixed by a clean install?
Its a minor annoyance for me, but for some of my clients that use this, its a serious problem.
Also, let me know if I posted this in the wrong place.
-
In 2.13, when I set up NAT rules, Firewall rules were automatically created. When the NAT rules were changed, or disabled/enabled, the firewall rules were altered accordingly.
They were not. At least not on my current 2.1.3 nanobsd and any previous versions they were not either.
-
In 2.13, when I set up NAT rules, Firewall rules were automatically created. When the NAT rules were changed, or disabled/enabled, the firewall rules were altered accordingly.
They were not. At least not on my current 2.1.3 nanobsd and any previous versions they were not either.
He may be talking about port forwarding?
-
Yes - every port forward created in the NAT section generates a firewall rule on the wan interface. Now if you disable the port forward, the firewall rule still shows as enabled, although it doesn't function anymore. This behavior is like this as I observed in 2.1, 2.1.1, 2.1.3.
