@rummonkey69 clean install and its works ok. doesn't work for me after doing an upgrade

In most cases, a cyberattack is almost impossible to notice. This operation takes place instantly and the user does not even understand how the intruders entered the system and control it. This situation happened in the office where I work a few months ago. Cybercriminals tried to get hold of our customer base and spread this information online. They penetrated the network and got all the access codes and passwords from our system, which is why the programs crashed and, by chance, they were unable to commit theft. Since then, we've turned to Cyber ​​Essentials to help protect and support our system from potential threats. I hope this will not happen again.

@nollipfsense Forum admin: please move to Installation and Upgrade ... thank you!

Hmm, I would not expect that to happen but I'm glad you found it and were able to resolve the problem. Steve

Yes, that's correct. It shows you can revert it because it's already in the base code in 2.5. Steve

Never mind, it's a bug in snmptt. As part of yesterday's festivities, the 1.4.2 update reached my box, and that has a bug that keeps it from working in daemon mode (no idea about standalone). If you find yourself in this situation, see https://sourceforge.net/p/snmptt/bugs/47/ for the fix.

@bmeeks said in 21.02/2.5 changes: @johnpoz said in 21.02/2.5 changes: edit2: As to when/if snort 3 might come to pfsense. You might want to ask in the ips/ids section. @bmeeks would be able to tell you if that is something that is on his roadmap for 2021 or if there is any sort of roadblocks to it, etc.. I just replied in a separate thread the poster created in the IDS/IPS forum. Snort3 is a no-go for me. I tried and failed and became completely disgusted with it last year. Converting the current package is a nightmare. I, personally, am not inclined at all to work on a Snort3 package. Others are welcome to try, though. If a multithread IDS is a must-have, then use Suricata as it is multithreaded. thank you for trying and giving the update

What if you try to run the upgrade from the console or SSH shell? pfSense-upgrade -d See also: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html

@bluepuma77 okay so it is working as you would like. Glad I could help you

@jimp Thanks. The good work on the date formats in the logfile is now live and in production on v2.5. Much appreciated.

NeVaR, it could be you didn't clean format (old disk partitions) your HDD. Try to format with diskpart and then reinstall pfSense.

@romor said in pfSense 2.5.0 release date?: but primary node after upgrade and reboot didn't start with error of unexisting KERNEL. :-/ The file - the kernel, wasn't there. That's most probably a file system error, a situation that can happens when the power fails. A preventive reboot just before upgrading will repair such a situation, as a 'fsck' is done before booting of the disk, repairing this issue (and DO check the boot log results before upgrading). Bringing hidden issues into the upgrade process is a bad idea. Not knowing what the state of a system is before upgrading is also not advisable. ( also : prepare a backup config - prepar an USB 'B' key with 2.4.5-p1 to be ready to get back in case of doubts ) @romor said in pfSense 2.5.0 release date?: upgrade of PROD firewalls isn't so good idea Wasn't that the reason why you use a master slave set up ? ;) It's actually a good idea to test the backup system. Btw : I do not have a master slave set up, so for me, it's will be the preparation as mentioned and the upgrade will be done tomorrow or Sunday, when the company's activity is less critical. @home, yesterday, things were way more easier, as I'm using a VM version. It was a matter of "click on upgrade" and yelling go-go-go-go because I didn't want to miss the Youtube feeds about the Perseverance touchdown. It was done within 10 minutes (I guess, didn't actual watch the upgrade process, I'll analyse the upgrade log this evening for events).

@jimp Thanks and thanks!

Great thanks all.

@chrullrich THANK YOU! That did the trick. Indeed the response from "pkg info" was as you stated. Once I set the update branch back to "2.4.5 DEPRECATED", the package manager once again worked as expected. Will this need to be undone once I decide to upgrade to pfSense 2.5.0? And agreed, the upgrade planning was bad. :/