Date: Sat, 20 Apr 2019 13:13:32 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Wojciech Puchar <wojtek@puchar.net> Cc: freebsd-hackers@freebsd.org Subject: Re: openvpn and system overhead Message-ID: <5CBAB88C.4020402@grosbein.net> In-Reply-To: <alpine.BSF.2.20.1904191841200.44949@puchar.net> References: <alpine.BSF.2.20.1904171707030.87502@puchar.net> <0cc6e0ac-a9a6-a462-3a1e-bfccfd41e138@grosbein.net> <alpine.BSF.2.20.1904191841200.44949@puchar.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19.04.2019 23:42, Wojciech Puchar wrote: >> because of unavoidable and big overhead due to constant context switching >> from user land to kernel land and back. Be it openvpn or another userland daemon. >> >> You need either some netmap-based solution or kernel-side vpn like IPsec (maybe with l2tp). > > well it has to cooperate with multitude of clients like windoze, > point&click routers etc. that's why openvpn. Windows has stock support for IPSec with and without L2TP and has no stock openvpn, so IPSec is more preferable. Cheap and slow SOHO routers generally have worst performance with openvpn that with any other kind of VPN, too.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5CBAB88C.4020402>