Alias FQDN Bug?
-
Hi there,
I'm not sure where I should report bugs to; sorry if this isn't the right place.
After upgrading our pfsense boxes to version 2.2.2, I found that the NAT rules on some of them stopped working.
I tried to pinpoint where the issue was and found that if I include an Alias with FQDN in the list, the firewall started to block that port after around 30 minutes or so. It does work initially. (Just to confirm, I did hit the apply update button each time I made the change)
In our case, the Alias was used as the Source Address. After removing the FQDN line from the list, it is still working after a day so I guess this is the culprit.The box is installed as a virtual machine on an ESXi 5.5 machine. The packages that are installed are Open VM Tools and OpenVPN Client Export package.
Please let me know if you need any other info.
Thank you. -
a moderator should/will move this (to wherever it belongs).
could you post some screenshots of the aliases / NAT rules ? (the ones that caused the issues). Are there any logs that might indicate a problem with the alias ?
-
https://redmine.pfsense.org/issues/4296
-
Thank you for your replies; now I know where to look for. :)
I think we'll wait for the release for 2.2.3 then, thanks again.