Looking to move pfsense from vm to hardware - solutions under $300?
-
mauroman, thank you for the correction. I scanned through the thread too fast :-[
Pippin, thank you for the confirmation, much appreciated.
-
Welcome.
One thing to add, keep in mind that this was without any other packages installed and no other traffic flowing.
-
There is the AES-NI support because the CPU is the Celeron N3150.
I did'nt pay customs fee because they have declared a value of USD30.I sent you a PM
-
There is the AES-NI support because the CPU is the Celeron N3150.
I did'nt pay customs fee because they have declared a value of USD30.I sent you a PM
I answered you
-
The second idea is the difference between 948 Mbps normal and 270 Mbps OpenVPN (unencrypted). Mainly caused by packets travelling between kernel and userland, and OpenVPN`s internal fragmenting and defragmenting, here CPU power (of single core!!!) comes into play.
When version OpenVPN 2.4 is ready, bringing AES-GCM, it is expected that throughput will go up.
The other issue probably related to process threading, the "pf" is now capable to support multi-threading, while as what I remember OpenVPN doesn't, for those low end ATOM devices we usually need 1-2 core's power to have NAT running at 1Gbps throughput, which means if we allow only single core operation the NAT probably will be cap at ~700Mbps, and OpenVPN will have more impact because it's adding burden on the CPU as well.
