Upgrade from 17.1.4 to 17.1.8 - NAT problem after upgrade

Started by bobbqzz, June 10, 2017, 05:57:25 PM

Previous topic - Next topic
Running into something odd, I recently upgraded from 17.1.4 to 17.1.8 and it appears as if NAT is no longer working correctly with virtual IPs.
I have NAT rules for my WAN IP for a host behind it (80,443).  I have similar rules for other VIPs and have not had any issues with this configuration.  Now on 17.1.8 all traffic that should be going to VIPs is going to my WAN IP instead.

Is there a way to correct the post upgrade configuration or is my previous configuration no loner supported?


i get the same thing. i think this is a bug

i may have to go back to pfsense until its sorted

Have either of you filed a bug report or checked to see if there's one already in existence? That would be the best place to get the developers attention.
Regards


Bill

June 25, 2017, 04:46:55 PM #4 Last Edit: June 26, 2017, 07:17:32 PM by jorgevisentini
.