But these are not strictly needed: any userspace with the right privileges and kernel calls can configure a WireGuard interface. WireGuard itself ships its own tools in the userspace package wireguard-tools: wg(8) and wg-quick(8). But it also has WireGuard specific attributes, which handle the VPN part of things.Īll of this can be configured via different tools.
It will have the usual attributes, like IP address, CIDR, and there will be some routing associated with it. It helps to think of WireGuard primarly as a network interface, like any other. Setting up the cryptographic keys is very much similar to configuring ssh for key based authentication: each side of the connection has its own private and public key, and the peers’ public key, and this is enough to start encrypting and verifying the exchanged traffic.įor more details on how WireGuard works, and information on its availability in other platforms, please see the references section. You get a network interface which encrypts and verifies the traffic, and the remaining tasks like setting up addresses, routing, etc, are left to the usual system tools like ip-route(8) and ip-address(8). WireGuard removed most of that complexity by focusing on its single task, and leaving out things like key distribution and pushed configurations. VPNs have traditionally been hard to understand, configure and deploy.
WireGuard is a simple, fast and modern VPN implementation, widely deployed and cross-platform. Multi-node Configuration with Docker-Compose
0 kommentar(er)
