4 ms·
Same here. Running of a $5/mo VPS and works fine. Wireguard is particularly helpful here, as I get about double the speed compared to openvpn (server-side CPU
by mises 7y ago
Same here. Running of a $5/mo VPS and works fine. Wireguard is particularly helpful here, as I get about double the speed compared to openvpn (server-side CPU bottleneck).
- chupasaurus 7y agoAES-GCM uses way less CPU, should check it out. WG with ChaCha-Poly consumes 4-5 times less (hadn't done benchmarks though, I just have Bandwidth meter and CPU% on my taskbar in Linux side-by-side).
- loeg 7y ago> AES-GCM uses way less CPU It depends on if you have AES-NI (for AES) and PCLMULQDQ (for GCM), or similar features on non-x86 architectures. Without them, AES-GCM is usually much slower than Chacha-Poly.
- out_of_protocol 7y agoAny ready to go setup instructions? For IPsec or OpenVPN it's a single bash script, hiding the complexity and the internal mess e.g. https://github.com/hwdsl2/setup-ipsec-vpn https://github.com/hwdsl2/setup-ipsec-vpn
- majewsky 7y agoThe good thing about WireGuard is that it doesn't really have any "complexity and [...] internal mess". A simple WireGuard setup with one client and one server has a 10-line configuration file on each side, with each side knowing their own private key and its peer's public key. I have not used WireGuard for the public VPN scenario, so I don't know if additional firewall rules are required to route traffic from VPN into the public internet, but I would guess as much.
- dewey 7y agoFrom my limited experience of setting it up the complexity is not in the configs files (also not with OpenVPN as you usually just copy paste some template anyway) but in setting up the routing, iptables etc.
- mises 7y agoIt's pretty easy; I suggest using wg-quick.