Update FAQ with IPv6 prefix policies for ULA addresses (#1083)

* Update FAQ with IPv6 prefix policies for ULA addresses

Most operating systems will prefer IPv4 rather than IPv6 ULA, which defeats the purpose of redirect-gateway ipv6. It's nothing the script can do to automate this.
s7r 2023-01-18 22:05:09 +00:00 committed by GitHub
parent 2a57e89489
commit 38d3bf9afa
No known key found for this signature in database
1 changed files with 22 additions and 0 deletions

View File

@ -151,3 +151,25 @@ route
So for example - here it would route all traffic of `` to the vpn. And the rest through the internet.
**Q:** I have enabled IPv6 and my VPN client gets an IPv6 address. Why do I reach the websites or other dual-stacked destionations via IPv4 only?
**A:** This is because inside the tunnel you don't get a publicly routable IPv6 address, instead you get an ULA (Unlique Local Lan) address. Operating systems don't prefer this all the time. You can fix this in your operating system policies as it's unrelated to the VPN itself:
Windows (commands needs to run cmd.exe as Administrator):
netsh interface ipv6 add prefixpolicy fd00::/8 3 1
edit `/etc/gai.conf` and uncomment the following line and also change its value to `1`:
label fc00::/7 1
This will not work properly unless you add you your VPN server `server.conf` one or two lines to push at least 1 (one) IPv6 DNS server. Most providers have IPv6 servers as well, add two more lines of `push "dhcp-option DNS <IPv6>"`