Adapt the wsl-vpnkit, so it makes use of WSL_INTEROP variable

[dabeck81]

Adapt the wsl-vpnkit, so it makes use of WSL_INTEROP variable and make it self-healing when the socket would be closed for one reason or another

[terlar]

I can confirm that this worked for me when running wsl-vpnkit as a systemd service. Thanks a bunch!

[Mansouu]

@dabeck81 I tried your solution, but afterwards the start fails with:
/app/wsl-gvproxy.exe is not executable due to WSL interop settings or Windows permissions

So, I commended out the check regarding wsl-gvproxy.exe and restarted it, but a have still the initial connection issues.

[dabeck81]

@dabeck81 I tried your solution, but afterwards the start fails with: /app/wsl-gvproxy.exe is not executable due to WSL interop settings or Windows permissions

So, I commended out the check regarding wsl-gvproxy.exe and restarted it, but a have still the initial connection issues.

Open up a shel-terminal and try to manually run following command /app/wsl-gvproxy.exe -help, it seems you have a different issue preventing to run exe-files than the problem I resolved with the wsl-interop variable.

[garysassano]

This worked for me using systemd with standalone script setup.

[Mansouu]

Open up a shel-terminal and try to manually run following command /app/wsl-gvproxy.exe -help, it seems you have a different issue preventing to run exe-files than the problem I resolved with the wsl-interop variable.

I had already done that at the time and it worked, so I knew it was a false positive and that's why I removed temporary the following check :

$GVPROXY_PATH -help 2>/dev/null
if [ $? -eq 1 ]; then
    echo "$GVPROXY_PATH is not executable due to WSL interop settings or Windows permissions"
    exit 1
fi

EDIT:
It looks like I'm not the only one with this problem. This is probably the same problem: #249 (comment)

[garysassano]

I experienced intermittent behaviour, and right now it completely stopped working:

wsl-vpnkit[2530047]: time="2023-12-01T12:34:16+01:00" level=error msg="cannot read size from socket: EOF"
wsl-vpnkit[2530047]: time="2023-12-01T12:34:17+01:00" level=info msg="waiting for packets..."
wsl-vpnkit[2557340]: /home/user/.wsl-vpnkit/wsl-gvproxy.exe: Invalid argument

[terlar]

Interesting, I had this working flawlessly for 2 weeks and since today I get that all the time.

[OrpheeGT]

#249 (comment)

[paddy74]

Adding that this PR fixed my issues with wsl-gvproxy.exe is not executable due to WSL interop settings or Windows permissions.