aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm2708
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2017-10-13 17:05:18 +0200
committerStijn Tintel <stijn@linux-ipv6.be>2017-10-16 14:01:21 +0300
commit699c6fcc314225f79156a26db418e15bbc6bf10f (patch)
treef5c200dc77c50bc83ac8b5866c1b73c0c78d561b /target/linux/brcm2708
parentfe3c3aed4454663d455af1216177d867ef4a7696 (diff)
downloadupstream-699c6fcc314225f79156a26db418e15bbc6bf10f.tar.gz
upstream-699c6fcc314225f79156a26db418e15bbc6bf10f.tar.bz2
upstream-699c6fcc314225f79156a26db418e15bbc6bf10f.zip
wireguard: add wireguard to base packages
Move wireguard from openwrt/packages to base a package. This follows the pattern of kmod-cake and openvpn. Cake is a fast-moving experimental kernel module that many find essential and useful. The other is a VPN client. Both are inside of core. When you combine the two characteristics, you get WireGuard. Generally speaking, because of the extremely lightweight nature and "stateless" configuration of WireGuard, many view it as a core and essential utility, initiated at boot time and immediately configured by netifd, much like the use of things like GRE tunnels. WireGuard has a backwards and forwards compatible Netlink API, which means the userspace tools should work with both newer and older kernels as things change. There should be no versioning requirements, therefore, between kernel bumps and userspace package bumps. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> Acked-by: Jo-Philipp Wich <jo@mein.io> Acked-by: Felix Fietkau <nbd@nbd.name>
Diffstat (limited to 'target/linux/brcm2708')
0 files changed, 0 insertions, 0 deletions