OpenVPN will eat cpu in userspace mostly so that one will most certainly find use for MP systems. IPSec runs in the kernel and will for a while be "limited" to one core, though for many applications, that one core will still do more crypto than needed, unless you are pushing it hard over the VPN.
For the secure remote management and/or monitoring things found on office vpns, and the occasional file data move on top of email, dns, and surfing, the limit on single core vpns when running on modern CPUs isn't that noticeable. 2015-09-02 3:16 GMT+02:00 Dot Yet <dot....@gmail.com>: > Any idea if running an ipsec vpn or openvpn on the same machine will > benefit from the second core? working remotely over VPN is quite common > these days. so all the extra juice may help encryption etc. is it so? > > On Tue, Sep 1, 2015 at 8:59 PM, Quartz <qua...@sneakertech.com> wrote: > > > Maybe this webpage would help you make an informed choice? > >> > >> https://calomel.org/pf_config.html > >> > > > > That looks like a good reference for setting up pf and the right way to > > architect your pf.conf, but it doesn't appear to address any of the cpu > > threading issues I'm trying to figure out. Thanks though, I'll keep a > copy > > of that in my files, it might help when we finally set this system up. > > -- May the most significant bit of your life be positive.
