Closed sahoahfoa closed 6 months ago
I'm also getting these same errors using the windows netclient. I can establish a connection and it's then goes to warning and then error.
[netclient.exe] 2022-08-03 11:25:40 error with start of Windows Netclient daemon: exit status 1 : '"C:\Program Files (x86)\Netclient\winsw.exe"' is not recognized as an internal or external command, operable program or batch file.
Also having this issue on Windows 11.
"C:\Program Files (x86)\Netclient\winsw.exe"' is not recognized as an internal or external command
Looking in that directory I do not see the winsw.exe file so the error makes sense. Not sure why it's not getting installed when doing the standard PowerShell install of netclient.
For what it's worth, I reinstalled netclient but using the msi based installer. (I did not uninstall the existing client first). That method did install winsw.exe as expected and running netclient pull afterwards is now working properly.
@sahoahfoa there have been lot of changes since v0.14.4, please try out the setup with latest version
Contact Details
Discord: Scottie#8631
What happened?
When joining my Windows 11 netclient to a second network the wg interface is not created and does not appear in
wg show
. dlrow_olleh on discord suggested changing the default port setting or enabling UDP punching for the second network . This fixed the issue and the interface was created when pulling the config again (I might have had to leave and rejoin actually). I'm assuming wireguard sees the second network pointing at the same endpoint and port and wont create the second interface. According to dlrow_olleh "netclient should check if the port is in use and use a different one"Version
v0.14.4
What OS are you using?
Windows
Relevant log output
Contributing guidelines