From e7b56130fdf409abe1b84639d5cc64b27d4ddb6e Mon Sep 17 00:00:00 2001
From: tastytea <tastytea@tastytea.de>
Date: Sat, 16 Feb 2019 03:25:30 +0100
Subject: [PATCH] Added information on how to turn SLAAC back on.

---
 .../wireguard-vpn-with-2-or-more-subnets.adoc    | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/content/posts/wireguard-vpn-with-2-or-more-subnets.adoc b/content/posts/wireguard-vpn-with-2-or-more-subnets.adoc
index 04fbc48..d34a8af 100644
--- a/content/posts/wireguard-vpn-with-2-or-more-subnets.adoc
+++ b/content/posts/wireguard-vpn-with-2-or-more-subnets.adoc
@@ -14,6 +14,8 @@ find an example how to do that, so I wrote this one.
 
 == Introduction
 
+This HowTo is Linux specific.
+
 I'm going to use the IP range `fd69::/48` for the VPN, `fd69:0:0:1::/64` for
 subnet 1 and `fd69:0:0:2::/64` for subnet 2. I'm going to call the server of
 subnet 1 `server1`, its first client `client1a`, the second one `client1b` and
@@ -48,6 +50,17 @@ sysctl -p /etc/sysctl.d/ip-forward.conf
 {{< / highlight >}}
 ----
 
+[NOTE]
+http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/[IP forwarding will put your computer into "router-mode"],
+it will no longer autoconfigure via https://en.wikipedia.org/wiki/SLAAC[SLAAC].
+If you need SLAAC, add this to `ip-forward.conf`:
+
+----
+{{< highlight cfg >}}
+net.ipv6.conf.all.accept_ra = 2
+{{< / highlight >}}
+----
+
 .`server1:/etc/wireguard/wg0.conf`:
 ----
 {{< highlight cfg >}}
@@ -161,4 +174,5 @@ by Stavros Korokithakis helped me a great deal in understanding WireGuard.
 
 == Updates
 
-* Updated 2019-02-16 to include IP forwarding
+* Updated 2019-02-16 to include IP forwarding.
+* Updated 2019-02-16 with information on how to turn SLAAC back on.