Closed jamilbk closed 10 months ago
This API function will probably do the trick. Just need to test it manually once. https://microsoft.github.io/windows-docs-rs/doc/windows/Win32/NetworkManagement/IpHelper/fn.CreateIpForwardEntry2.html
Powershell takes about 800-900 ms, shouldn't be hard to beat
13,000 ms to about 200 ms. It wasn't critical but I need to bring the tunnel up and down a lot for DNS testing so that 13 seconds really adds up.
13,000 ms to about 200 ms
Awesome work! Seconded re: IPv6. Even though it's not working currently it's probably good to make sure the linked PR doesn't further prevent it from doing so.
What does route print
show?
@jamilbk The IPv6 bug was simple so I have a fix in PR #3120
Wintun just wasn't setting the tunnel's IPv6 address correctly, it had the wrong syntax for netsh
Shelling out to
netshPowershell's New-NetRoute is slow.