Keiichi Shimamura
Keiichi Shimamura
Have you tried using the wsl-vpnkit with the auto-generated resolv.conf or `192.168.67.1`?
`192.168.67.1` or the auto-generated resolv.conf with wsl-vpnkit should direct your DNS requests from WSL 2 to the `wsl-gvproxy.exe` process on the Windows host to be resolved. For most situations, this...
With wsl-vpnkit running. VPN on, wsl-vpnkit on.
Closing due to inactivity
You could try v0.2.x, which uses a different codebase and might not trigger your AV. FWIW most AV vendors do not flag `wsl-gvproxy.exe` v0.3.2 as malicious. https://www.virustotal.com/gui/file/4cd8c7532b286040b1d7bbe19bb2f79ad56e0c4ec9876eb2448174d0bd1e8fad
Closing due to inactivity.
> It looks like sakai135 has forked and compiled vpnkit.exe binaries and made available, but I agree, it would be much better to be able to get the binary directly...
@junquero You can download the package from https://github.com/fdopen/ocaml/releases/4.07.0-1
From the logs, it seems to be working. What issues are you having?
Can you try `nslookup -type=A example.com` and `nslookup -type=A example.com 1.1.1.1` and see if they work. Did you make any changes to DNS resolution on your distro like editing `/etc/resolv.conf`?...