From bab4e14828e36f3bf86f3d2a8ae55b84b996a672 Mon Sep 17 00:00:00 2001 From: Juan Font Date: Sun, 7 May 2023 11:13:03 +0000 Subject: [PATCH] Further clarification on unsupported ranges in config example --- config-example.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/config-example.yaml b/config-example.yaml index 22cb09a..241c84b 100644 --- a/config-example.yaml +++ b/config-example.yaml @@ -58,11 +58,12 @@ noise: # List of IP prefixes to allocate tailaddresses from. # Each prefix consists of either an IPv4 or IPv6 address, # and the associated prefix length, delimited by a slash. -# While this looks like it can take arbitrary values, it -# needs to be within IP ranges supported by the Tailscale -# client. +# It must be within IP ranges supported by the Tailscale +# client - i.e., subnets of 100.64.0.0/10 and fd7a:115c:a1e0::/48. +# See below: # IPv6: https://github.com/tailscale/tailscale/blob/22ebb25e833264f58d7c3f534a8b166894a89536/net/tsaddr/tsaddr.go#LL81C52-L81C71 # IPv4: https://github.com/tailscale/tailscale/blob/22ebb25e833264f58d7c3f534a8b166894a89536/net/tsaddr/tsaddr.go#L33 +# Any other range is NOT supported, and it will cause unexpected issues. ip_prefixes: - fd7a:115c:a1e0::/48 - 100.64.0.0/10