Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

dabeck81
Copy link

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

…e it self-healing when the socket would be closed for one reason or another
@terlar
Copy link

terlar commented Nov 17, 2023

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

wsl-vpnkit Outdated Show resolved Hide resolved
…e it self-healing when the socket would be closed for one reason or another
wsl-vpnkit Outdated Show resolved Hide resolved
…e it self-healing when the socket would be closed for one reason or another
@Mansouu
Copy link

Mansouu commented Nov 24, 2023

@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
Copy link
Author

@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
Copy link

This worked for me using systemd with standalone script setup.

@Mansouu
Copy link

Mansouu commented Nov 27, 2023

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
Copy link

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
Copy link

terlar commented Dec 1, 2023

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

@OrpheeGT
Copy link

OrpheeGT commented Dec 4, 2023

#249 (comment)

@paddy74
Copy link

paddy74 commented Jan 29, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants