Tailscale uses the IPv6 subnet address to route your tailnet traffic to the appropriate IPv4 YYYY:YYYY is the IPv4 address represented as 16 bit hex numbers.įor example, this would be the IPv6 subnet route for a site with ID 7 and IPv4 subnet address.A site ID of 0 is valid, but note the resulting IPv6 address, while allowed, would have an empty string for the translator identifier: fd7a:115c:a1e0:b1a ::YYYY:YYYY. For example, you might want to use 1 for your first subnet route, so the translator identifier would be 0:1. You choose which site IDs to assign to your subnet routes. Only the lower 8 bits may be used to specify a site ID-allowed The site ID is the location that the IPv6 packets shouldĪrrive at before being translated to IPv4. 0:XX is the 32-bit translator identifier.fd7a:115c:a1e0:b1a is the 64-bit fixed prefix used for Tailscale 4via6-routed packets.The Tailscale-specific IPv6 subnet address is of the form: Have the IPv6 packets rewritten by Tailscale for IPv4, so the IPv4 addresses do not need to be changed. Devices connecting to the IPv6 subnet router will When you use this feature, your subnet router advertises an IPv6 subnet (using a Tailscale-specificĪddress) that maps to the desired IPv4 subnet.

A partner or contractor network contains subnets with IP or CIDR ranges that overlap those of an organization that would like to share access.Cloud resources or SaaS apps are rolled out to a network that contains subnets with overlapping IP or CIDR ranges.A network contains subnets with overlapping IP or CIDR ranges.To try it, follow the steps below to enable it for your network using Tailscale v1.24 or

Easyvpn overlapping subnets