@tagit446 forgot to tell, don't forget to enable log for these rules.

@bob-dig thanks that worked deleting the files there in the db... after deleting it changed everything to .localdomain and then after another 10 min it renamed everything to the localhost names so i dunno why it was going crazy with the number or so.. but deleting fixed it.. i was going crazy shutting off everything refreshing clearing rebooting pfsense 3 times nothing had solved it but deleting thoses files did

@johnpoz I know this is old but THANK YOU! I was seeing a million of these entries on a bunch of interfaces, LAN, S2S_VPNs, etc on ONLY ONE of my pfSense appliances and couldn't figure out what the hell was going on!

@kom I'm learning that. Thanks for your help with this.

@balanga Enter "CSRF check failed" in your favourite search engin, and find articles like this : https://stackoverflow.com/questions/57048799/what-is-csrf-check-failed-when-going-on-a-website-which-doesnt-require-login

Yeah pkg/pkg-static is required to run the upgrade so it must be functional. Reinstalling and restoring the config is often faster and easier if you've ever done it before. Steve

@trickyt I used good old "dd" on my Mac and it does the job every time. balenaEtcher is probably safer from typos however.

Yeah that should be update version, so you were on something previous to 2.4.5p1? And it updated to that? Were you on 2.4.4p3? You have not provided an abundance of information here.. What did it actually update, if it updated packages without upgrading the base version you could have some issues. 2.4.5_1 is not current.. But is supported still, if you would like to stay on that version.. And you have it set in your upgrade settings to stay on that version.. You should be fine.

I'm trying to wake up the whole lan too using this command : php /usr/local/www/services_wol.php wakeall=true But it doesn't work.... Have anyone any idea that could help?

@am-steen Only you installing nmap / ncat / netcat and you trying from the internet yourself.

NAT on non-default routes is fixed in 21.02.2. The Arm7 Snort issue is still outstanding. We are aware of the impact there and are working to address it. Steve

@brucexling said in Printers Not on Current VLAN: I have read some accounts that it can be problematic trying to print to a printer not on the current network. This is the case if your trying to use L2 discovery to find the printer in the first place. Airprint for example will not work across vlans. But printing across vlans is not problematic - if you are printing to the IP or the fqdn that resolves to the IP of the printer. And the appropriate firewall rules are in place to allow the ports your using for your printing protocol.

@gfeiner Same set up that I have for my OPT.

@viragomann OK many thanks to you and to Mr. SteveITS also you helped me so much.

@itpp21 Maybe if you have read up before posting you would understand why the suggestion. https://docs.netgate.com/pfsense/en/latest/recipes/example-basic-configuration.html