Upgrade from 2.4.4-p3 to 2.5
-
Right! Let's repeat:
Version 2.5 is still in snapshot state. No Beta, no ReleaseCandidate!
-
But thanks for testing!
Steve
-
So far rock stable and no problems om my hp server i am using it on
-
I have a multicore cpu 6 core 12 thread cpu and from what i see is version 2.5 is utilizing the cores better than 2.4.4-p3 .And still no problems
-
The development team should get on the ball and release pfSense 2.5...some folks, such as I and others (OP), had already prepared for it with newer equipment then got the disappointed news that pfSense 2.5 won't require AES-in.
-
Yes i upgraded also to new hardware and with the announcement I was not to happy because my hardware is ready for AES
-
Why is the requirement of aes-ni so significant fails me.
AES hardware crypto offload is supported for quite some time now. Making it an absolute requirement certainly won't make any difference to the folks that already have aes-ni capable hardware. -
@netblues said in Upgrade from 2.4.4-p3 to 2.5:
Why is the requirement of aes-ni so significant fails me.
AES hardware crypto offload is supported for quite some time now. Making it an absolute requirement certainly won't make any difference to the folks that already have aes-ni capable hardware.That's true; however, for over a year and a half the requirement to upgrade to pfSense 2.5 was AES-in...so, folks who wanted to continue growing with pfSense and didn't already had hardware capable for that requirement needed to get new/old hardware to meet pfSense 2.5.
-
@NollipfSense And it was good they did. They benefit from much better vpn encryption performance.
The fact that dropping support for non aes-ni capable hardware could make the community smaller jeopardizing the longlivity and future of pf, is a far bigger problem. -
@netblues said in Upgrade from 2.4.4-p3 to 2.5:
@NollipfSense And it was good they did. They benefit from much better vpn encryption performance.
The fact that dropping support for non aes-ni capable hardware could make the community smaller jeopardizing the longlivity and future of pf, is a far bigger problem.In this case, have two versions for a win win. The new folks who just spend money upgrading could quickly jump ship limiting pfSense growth potential.
