825071750290210916 #windows

few-airline-95046

03/02/2022, 8:51 PM

What exactly happens when initiating a pull? I noticed that when I try a pull the status for the node goes back to healthy, but as the pull never completes it goes back to warning (and eventually error I assume)

quiet-continent-24852

03/02/2022, 9:05 PM

I have found the error

quiet-continent-24852

03/02/2022, 9:06 PM

it's unable to tear down the wireguard interface, which it does in the case of a pull and continually checks until it's tore down, which is why it's "paused". So our tear down logic is failing for some reason, will fix momentarily I think

jolly-london-20127

03/02/2022, 9:11 PM

for the record I would like to state that the windows bug is my fault and zebraman is smarter than me

jolly-london-20127

03/02/2022, 9:12 PM

i put in a hotfix for openwrt which caused windows to use some linux commands

quiet-continent-24852

03/02/2022, 9:17 PM

alright @User and @User I put a patched version in the v0.11.0 release, but officially the fix will be in v0.11.1

bored-island-21407

03/02/2022, 9:18 PM

windows should just switch to linux commands (and paths). It would make everyones life easier.

jolly-london-20127

03/02/2022, 9:20 PM

agreed, really this my fault, we need to open an issue against the windows kernel to make it unix compatible

few-airline-95046

03/02/2022, 9:34 PM

Do I need to uninstall netclient first, and then re-run the powershell install client command?

bored-island-21407

03/02/2022, 9:38 PM

yes, otherwise a join will use the new version but the daemon will be executing the old version

quiet-continent-24852

03/02/2022, 9:51 PM

well

quiet-continent-24852

03/02/2022, 9:51 PM

download the new one

quiet-continent-24852

03/02/2022, 9:52 PM

and run uninstall from it

quiet-continent-24852

03/02/2022, 9:52 PM

the old one doesn't uninstall properly

quiet-continent-24852

03/02/2022, 9:52 PM

@User

few-airline-95046

03/02/2022, 9:59 PM

Aha! Alright, will test that

handsome-lifeguard-70799

03/02/2022, 10:09 PM

Thanks all, will try tomorrow!

few-airline-95046

03/02/2022, 10:36 PM

@User , so I grabbed the netclient.exe from the v0.11.0 tag on github, uninstalled (which seem to have gone well), and then ran the client install command in powershell. It downloaded netclient, started up but it seem to hang at "2022/03/02 23:32:56 [netclient] node created on remote server...updating configs"

quiet-continent-24852

03/02/2022, 10:53 PM

When you uninstalled, were the wg interfaces still present? If so you may have needed to manually uninstall them

handsome-lifeguard-70799

03/03/2022, 8:56 AM

@User new netclient 0.11 is now working for pull and resetting the wg interface 🥳

few-airline-95046

03/03/2022, 9:31 AM

Got it working as well 🙂

handsome-lifeguard-70799

03/03/2022, 10:34 AM

Nice. All nodes nice and stable for a couple of hours now

few-airline-95046

03/03/2022, 12:08 PM

Hmm, I was too quick to judge...Still having issues with the status going to warning/error. Tried uninstall everything (wireguard and netclient) on the windows machine and install again, but still get the netclient stuck in "node created on remote server...updating configs" when re-installing.

handsome-lifeguard-70799

03/03/2022, 12:13 PM

I've managed to get three windows machines in different locations all ticking away happily today @User

few-airline-95046

03/03/2022, 12:13 PM

Which version of Windows are you running?

handsome-lifeguard-70799

03/03/2022, 12:14 PM

Here's what I did: downloaded the latest v.0.11.0 netclient from the Github page manually and replaced netclient.exe in C:/windows/system32

handsome-lifeguard-70799

03/03/2022, 12:17 PM

powershell admin, .\netclient leave -n my-net; .\netclient uninstall; remove any interfaces in the wireguard app - if none are showing, check the wireguard app logs tab - if it's still logging as it was on one of mine then reboot; then run the powershell command from the access keys page to join ; update your node in the UI for listening port or UDP hole punching, and anything else needed; then .\netclient pull - should update configs for your comms and actual network and reset the wireguard interface

few-airline-95046

03/03/2022, 12:18 PM

Thanks for your successful steps, I'll try that 🙂

few-airline-95046

03/03/2022, 12:52 PM

So far so good...also did a reboot after uninstalling netclient and making sure that no interfaces was left in wireguard. Now it installed fine and the pull worked as well... 🙂

few-airline-95046

03/03/2022, 12:54 PM

One question though...every time the powershell command from the access keys page is run, a netclient.exe is saved to your current path...is that file still used after everything is up and running, or is everything executed from the C:\ProgramData\Netclient folder then?