fast (low latency and line-rate bandwidth).robust automatic reconnects after reboots / network downtime / NAT connection table drops.ability to some traffic or all traffic to/through arbitrary hosts on the VPN LAN.ability to easily create a LAN like 192.0.2.0/24 between all servers, or more complex networks using custom routes.behaves like a normal ethernet interface, behaves well with standard kernel packet routing rules.minimal key management work needed, just 1 public & 1 private key per host.minimal config, low tunable surface area and sane defaults.Whether living behind the Great Wall of China or just trying to form a network between your servers, WireGuard is a great option and serves as a 'lego block' for building networks (much in the same way that ZFS is a lego block for building filesystems). My Personal Requirements for a VPN Solution.

See for example code and documentation source. I routinely get sub 0.5ms pings and 900mbps+ on good connections. simple CLI and seamless integration with system networking.simple internals and small protocol surface area.fast, both low-latency and high-bandwidth.

As of 2020-01 it's been merged into the 5.6 version of the Linux kernel, meaning it will ship with most Linux systems out-of-the-box.

It shares some similarities with other modern VPN offerings like Tinc and MeshBird, namely good cipher suites and minimal config. WireGuard is an open-source VPN solution written in C by Jason Donenfeld and others, aiming to fix many of the problems that have plagued other modern server-to-server VPN offerings like IPSec/IKEv2, OpenVPN, or L2TP. Source for these docs, example code, and issue tracker: This is my solo unofficial attempt at providing more comprehensive documentation, API references, and examples. API reference guide for WireGuard including Setup, Configuration, and Usage, with examples.Īll credit goes to the WireGuard project, zx2c4 and the open source contributors for the original software,

Wireshark no interfaces found reddit