* tools/testing/selftests/wireguard/netns.sh: Aforementioned testing * selftest/*.h: Runtime unit tests for some of the most security * main.c, version.h: Initialization and deinitialization of the module. * timers.: Uses the timer wheel to implement protocol particularĮvent timeouts, and gives a set of very simple event-driven entry Also handles receiving handshake and cookie messages The rest of the networking subsystem with GRO via the typical NAPI Multiple cores, before passing them off in order to be ingested via * receive.c: Handles decrypting incoming packets in parallel on Messages as part of the protocol, in parallel. Also handles sending handshake and cookie Multiple cores, before sending them in order on a single core, via * send.c: Handles encrypting outgoing packets in parallel on
The various queues used in the multicore algorithms. * queueing.: Shared function on the rx and tx path for handling Tools and network management utility, and the WireGuard project The API has been implemented by several userspace * netlink.: Userspace API entry point for configuring WireGuard Socket routing semantics for the automatic roaming. The general set of kernel socket APIs, for sending and receivingĬiphertext UDP packets, and taking care of WireGuard-specific sticky * socket.: Implementation of functions related to udp_socket and * peer.: Each interface has a list of peers, with helper functionsĪvailable here for creation, destruction, and reference counting. Rtnl, responsible for maintaining the life of a given interface and * device.: Implementation of functions for the netdevice and for Integral part of the design of the protocol, and the latter justīeing nice helper functions around the specific hashtables we use. WireGuard, the former being trie-like with particular semantics, an
* allowedips., hashtables.: The main lookup structures of Ratelimiting certain types of cryptographic operations in accordance
* ratelimiter.: Used as an integral part of cookie. They also handle reference counting for their various shared Nature, taking in buffers of bytes and spitting out buffers ofīytes. * noise., cookie., messages.h: These implement the bulk of theĬryptographic aspects of the protocol, and are mostly data-only in Making auditing and comprehension easier. Into a single file, WireGuard is developed as cleanly separable files,
#N2ping vpn code#
The source code is fairly short, but rather than combining everything Namespace the WireGuard interface was originally created, exactly like Of the fact that sockets used by WireGuard intentionally stay in the Tests and out-of-kernel tests based on network namespaces, taking profit This commit also comes with several different tests, both in-kernel The Netlink maintainer a year ago, several high profile userspace Operations, but it is implemented modestly using workqueues and NAPI.Ĭonfiguration is done via generic Netlink, and following a review from System designed for maximum throughput and minimal latency of encryption It has a somewhat novel multicore queueing Makes use of the udp_tunnel APIs, GRO, GSO, NAPI, and the usual set of This commit implements WireGuard as a simple network device driver,Īccessible in the usual RTNL way used by virtual network drivers. The kernel, that aims to be much simpler and easier to audit than IPsec.Įxtensive documentation and description of the protocol andĬonsiderations, along with formal proofs of the cryptography, are WireGuard is a layer 3 secure networking tunnel made specifically for Subject: net: WireGuard secure network tunnelĭate: Tue, 16:56:22 +0200
#N2ping vpn archive#
Donenfeld archive mirror help / color / mirror / Atom feed From: "Jason A. Net: WireGuard secure network tunnel - Jason A.
0 kommentar(er)
