<![CDATA[DMZ no longer working after upgrade to 2.5.1]]>

<![CDATA[DMZ no longer working after upgrade to 2.5.1]]>Hi guys,

I have upgraded our pfsense to 2.5.1. The upgrade went well but after the reboot our DMZ stops working. I have 3 virtual IP's that I port forward to. After the upgrade the 3 servers cannot be accessed from the outside. When I check the firewall logs I get the "Block drop in log inet all label. Default deny rule IPv4." I even tried installing 2.5.1 from scratch and setting everything back up from new but same problem. Is there a problem with 2.5.1 or a feature been added that I need to configure?

Thanks in advance,

]]>https://forum.netgate.com/topic/164914/dmz-no-longer-working-after-upgrade-to-2-5-1RSS for NodeWed, 13 May 2026 14:03:18 GMTWed, 07 Jul 2021 01:44:56 GMT60<![CDATA[Reply to DMZ no longer working after upgrade to 2.5.1 on Wed, 07 Jul 2021 03:16:25 GMT]]>Do you have a multi-WAN configuration? If you do, there is a known bug in 2.5.1 with port-forwarding and a multi-WAN setup. The bug is fixed in the 2.5.2-RC (that will be released soon). Here is that bug report: https://redmine.pfsense.org/issues/11805.

]]>https://forum.netgate.com/post/990983https://forum.netgate.com/post/990983Wed, 07 Jul 2021 03:16:25 GMT