From f07138d2d70030fa5fde9001eecf1f60acd70903 Mon Sep 17 00:00:00 2001 From: Julien Dessaux Date: Tue, 28 Feb 2023 22:52:10 +0100 Subject: add wireguard ipv6 blog article --- content/blog/miscellaneous/wireguard-routing-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/blog/miscellaneous/wireguard-routing-2.md') diff --git a/content/blog/miscellaneous/wireguard-routing-2.md b/content/blog/miscellaneous/wireguard-routing-2.md index ff8aba1..a4e8ec5 100644 --- a/content/blog/miscellaneous/wireguard-routing-2.md +++ b/content/blog/miscellaneous/wireguard-routing-2.md @@ -129,7 +129,7 @@ AllowedIPs = 10.1.2.3/32 You might have feared this would be the most complicated configuration but it is the simplest: every peer has a `/32` netmask. The only thing to note is that we do not specify an endpoint for Adolin and Baon since they are behind a home network's NAT. -The only additional thing we need is to enable routing on Elend so that it can forward traffic (firewalling is the subject of the next article). This can be done by setting the right sysctl value depending on your operating system: +The only additional thing we need is to enable routing on Elend so that it can forward traffic (firewalling is the subject of a next article). This can be done by setting the right sysctl value depending on your operating system: - FreeBSD: set `gateway_enable="YES"` in your `/etc/rc.conf` - Linux: set `net.ipv4.ip_forward=1` in your `/etc/sysctl.conf` - OpenBSD: set `net.inet.ip.forwarding=1` in your `/etc/sysctl.conf` -- cgit v1.2.3