Hi,
unless I am mistaken, this is now the third time a user is reporting something like this (see this and this thread for the other two incidents).
In the past, both issues turned out to be user configuration errors not induced by any firewall rule created via IPFire’s web interface, but by editing firewall.local or similar things (which we strongly recommend against for a good reason).
So, let’s figure out what goes wrong this time…
Please don’t do so until we traced down the problem. 
@elpellini: Could you please run iptables -L -n -v on our IPFire machine and post it’s results here? Feel free to scrub any public IP addresses, if necessary. Did you made changes to your IPFire system directly via SSH? If so, which?
Thanks, and best regards,
Peter Müller