Filter Rule Association seemingly changing itself

[david tallacksen]

I have a pretty basic setup, using PFSense 2.3.4. I do have rules to allow traffic to a local ftp server and other such resources.

Recently we weren't able to access the FTP, and it turned out the filter rule association was set to 'none'. Mind you, it's worked for years previously. We changed it, and then also changed the password for the one (admin) user we have, just in case security was somehow compromised.

However, seemingly randomly, the setting has been changed back a number of times in the past week.

Any ideas what would cause this? We aren't making any other changes to PFSense.

I know it sounds crazy, but I just can't make sense of it.

Thanks for any and all ideas.

[jimp]

What exactly are you picking for the option when you set it?

If you choose "Add unassociated filter rule" it will make a rule but not maintain the association, so the NAT rule will say "None" the next time you load the rule.

Also if the associated rule was made on an earlier version a long time ago before the association code was working properly, it's possible it didn't maintain the association.

If all else fails, delete the NAT rule, firewall rule(s), and make a fresh NAT rule using the default associated rule option (leave it as-is), and that should work.