Closed lzlrd closed 5 years ago
Windows doesn't add the default route for ipv6. I'll prepare a fix for the powershell script, but for now you can use the following workaround:
::/0
does'n work for some reason.
Add-VpnConnectionRoute -ConnectionName "<algo connection name>" -DestinationPrefix ::/1
Add-VpnConnectionRoute -ConnectionName "<algo connection name>" -DestinationPrefix 8000::/1
Change <algo connection name>
to your connection name
@lazerl0rd Does it work for you? https://github.com/trailofbits/algo/pull/1490
We've decided to deprecate IKEv2 for windows https://github.com/trailofbits/algo/issues/1493
@jackivanov sorry, it does work. Sad to see it’s deprecated as WG for Windows is still a bit buggy in it’s stopping and starting and the Wintun drivers are seemingly causing issues with some unreleased software I’m testing.
Describe the bug
When connecting via IPSec to the VPN on Windows where my physical network is IPv4 only, I do not end up with a dual-stack connection.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A dual-stack connection after routing through the VPN.
Additional context
As above, my physical network is IPv4-only. I DO get an IPv6 address using Wireguard on my Android device (kernel-level [rooted] wireguard) and my iPad (iOS wireguard client).