Hello, I noticed that issuing the following command in the server config:
push "route-ipv6 ::/0 2001:648:2000:ffae::1 15" does indeed make a windows client install that route, but it ignores the metric: add_route_ipv6(::/0 -> 2001:648:2000:ffae::1 metric 15) dev Local Area Connection 3 C:\Windows\system32\netsh.exe interface ipv6 add route ::/0 Local Area Connection 3 fe80::8 store=active Issuing route print client-side confirms that suspicion. 13 26 ::/0 fe80::208:7cff:fe63:e400 14 286 ::/0 fe80::8 (13 is my lan, 14 is the tun device. As you can see, metric is 286) I suppose most people on this list should be aware of the problem. If you desire so, I'd gladly file a bug request. Fwiw, I was able to workaround this problem by pushing two /1 routes, exactly like def1 does for IPv4. Like this: push "route-ipv6 ::/1 2001:648:2000:ffae::1" push "route-ipv6 8000::/1 2001:648:2000:ffae::1" Apologies if this has been discussed before. Kind regards to all, -- Athanasios Douitsis
