2.4.5 is broken in so many ways
-
I know you guys work hard to make Pfsense what it is but 2.4.5 must be the most broken update in the 10 years I've been using Pfsense that I've ever seen.
I've never been up all night before just trying to reinstall and restore a config in my life!
IF it boots to the drive correctly the restore fails due the the router being unable to access the internet.
Delete all the interface rules does nothing to stop the default block rule from blocking LAN traffic and allowing the any any rule to work.
Bogon blocking spikes network latency and blocks legitimate IP addresses.
There's unexplained latency spikes and packet loss
Packages can't reinstall because the server is unreachable or the certificate is invalid.
Are you guys getting ready to sell Netgate/Pfsense because the only time I ever see things go this sideways is when the ship is either going down or being sold.To others that see this post, stay away from 2.4.5.
To those that 2.4.5 seems to be working for, good, I'm glad it's working for someone but I've had it mess up more that one machine so far. -
my box has been running flawlessly since 2.4.5 was released.
p1 should be out next week i am guessing
-
Mine too.
-
Only issue so far I have come upon, is the bogonlist/multiple core issue. On one core it runs reasonably stable....
-
There is pretty much nothing different in 2.4.5 regarding the installation and configuration, Whether or not it has WAN access or not, etc.
In fact, 2.4.4-p3 and 2.4.5 use the same configuration version, 19.1. You can generally use a 2.4.5 configuration on 2.4.4-p3 and vice-versa.
Yes, the pfctl issue is a drag. 2.4.5-p1 will be released "soon." (When it's ready) and all indications are that problem has been solved.
