[Bug]: Windows Netclient not setting routes

gravitl / netmaker

Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.

https://netmaker.io

Other

9.44k stars 550 forks source link

[Bug]: Windows Netclient not setting routes #1896

Open kpestalozzi opened 1 year ago

kpestalozzi commented 1 year ago

What happened?

We use a Egress Gateway to connect to our Office Networks. After boot or when changing networks (e.g. LAN to WLAN) netclient does not set the routes for the egress networks. The Wireguard tunnel comes up fine and the route for the VPN itself exists but all routes for the egress networks are missing. After doing a netclient pull manually the routes are set correctly. This problem seems only to exist on Windows. I couldn't reproduce this on Linux.

Version

v0.17.1

What OS are you using?

Windows

Relevant log output

No response

Contributing guidelines

[X] Yes, I did.

FreeMinded commented 1 year ago

Maybe related with this #1867?

Elf36 commented 1 year ago

I have this issue - any progress ?

zzecool commented 1 year ago

I have the same exact issue with Netclient in windows 11, it doesnt create router even with a manuall netclient.exe pull.

I dont think anyone actually testing the clients as the last 5 clients desnt even show the host settings from the gui.

jivanyatra commented 1 year ago

@zzecool - I opened a new bug that may be the same or related. Could you try my workaround and see if it works for you?

Start > search for Command Prompt > Open as Administrator (if you can?)

cd to C:\Program Files (x86)\Netclient\

enter netclient.exe pull and see what happens? I manually did a netclient.exe join -t ENROLLMENT_KEY and I'm connected, even if the gui isn't working at all.

jivanyatra commented 12 months ago

I updated my ticket with what worked for me. Again, not 100% sure we're seeing the same issue, but for what it's worth, when I do netclient.exe pull it works now.

tompkinss-decian commented 10 months ago

Unable to connect to egress routes from Windows on latest version (v0.21.2); it doesn't create the routes correctly, which can be confirmed via route print... I was able to solve via this change to wireguard\wireguard_windows.go. I may get around to contributing properly with a PR, but here is the effective change in case anyone else wants to run with it.

uGiFarukh commented 10 months ago

This PR should fix this problem on windows -> https://github.com/gravitl/netclient/pull/630