825071750290210916 #windows

handsome-lifeguard-70799

03/17/2022, 11:34 AM

I've rebooted, removed wireguard, reinstalled, etc. Any pointers appreciated!

few-airline-95046

03/17/2022, 11:35 AM

I saw that issue yesterday when fiddling about. In that case it was that my comms network had UDP hole punching disabled. After I enabled it again the windows node could join

handsome-lifeguard-70799

03/17/2022, 11:37 AM

Thanks, UDP hole punching is enabled on the comms network though

handsome-lifeguard-70799

03/17/2022, 11:37 AM

Makes me wonder if the new comms network needs to be explicitly added in the windows firewall like the main network

handsome-lifeguard-70799

03/17/2022, 11:37 AM

I'll try that now

jolly-london-20127

03/17/2022, 11:37 AM

hmmm we had that issue with windows but it should have been hotfixed the day of the release

few-airline-95046

03/17/2022, 11:38 AM

By the way @User, is it possible to leave the comms network without running netclient uninstall?

handsome-lifeguard-70799

03/17/2022, 11:39 AM

Good to know, but I've definitely deleted the binary in both locations and pulled down the latest again. Unless the scripts are still pulling the older version somehow?

few-airline-95046

03/17/2022, 11:40 AM

Have you tried wiping programdata\netclient?

handsome-lifeguard-70799

03/17/2022, 11:40 AM

Yup, everything

handsome-lifeguard-70799

03/17/2022, 11:40 AM

Also checked for old tunnels in wireguard, nothing there or logging, and old interfaces in windows

jolly-london-20127

03/17/2022, 11:45 AM

I will test it out this morning to try replicating

handsome-lifeguard-70799

03/17/2022, 11:48 AM

thanks @User

handsome-lifeguard-70799

03/17/2022, 11:51 AM

@User got it working. something going on with the script or some kind of caching perhaps

handsome-lifeguard-70799

03/17/2022, 11:54 AM

I've uninstalled and deleted the binary again to test, running the powershell script again

handsome-lifeguard-70799

03/17/2022, 11:55 AM

Downloading directly from GitHub and moving it over by hand got me onto my network

jolly-london-20127

03/17/2022, 11:55 AM

i've found powershell to be super frustrating for this reason...we are not powershell experts...if someone could help us out with that I think we could make installs a lot smoother on windows

handsome-lifeguard-70799

03/17/2022, 12:01 PM

That's confirmed, see if you can replicate. PowerShell script is downloading a netclient.exe that is setup differently to manually downloading from GitHub. Looks like security settings might be the issue, they look pretty different. This could be Windows Server 2016 thing, or how we have our server configured even

jolly-london-20127

03/17/2022, 12:02 PM

maybe we just need to modify the powershell script to download without cache

handsome-lifeguard-70799

03/17/2022, 12:07 PM

The binaries appear to be identical, but I can't join my network with the one downloaded from the powerShell script, even after having overwritten it with one downloaded directly from releases (i.e. leaving again and re-testing the powershell script to eliminate caches on my side)

handsome-lifeguard-70799

03/17/2022, 12:08 PM

If you get a chance to update the version numbers in the binaries, that might help a bit. still says 0.8.5 in all recent versions

jolly-london-20127

03/17/2022, 12:18 PM

you mean when you run netclient.exe --version?

jolly-london-20127

03/17/2022, 12:18 PM

it should not...

handsome-lifeguard-70799

03/17/2022, 12:22 PM

More problems: even after joining both networks and seeing the node in the UI

handsome-lifeguard-70799

03/17/2022, 12:22 PM

2022-03-17 12:19:43.712783: [TUN] [nm-mat] Starting WireGuard/0.5.3 (Windows Controller 10.0.14393; amd64)
2022-03-17 12:19:43.712783: [TUN] [nm-mat] Watching network interfaces
2022-03-17 12:19:43.715786: [TUN] [nm-mat] Resolving DNS names
2022-03-17 12:19:43.715786: [TUN] [nm-mat] Creating network adapter
2022-03-17 12:19:43.861149: [TUN] [nm-mat] Using existing driver 0.10
2022-03-17 12:19:43.872401: [TUN] [nm-mat] Creating adapter
2022-03-17 12:19:44.182958: [TUN] [nm-mat] Using WireGuardNT/0.10
2022-03-17 12:19:44.182958: [TUN] [nm-mat] Enabling firewall rules
2022-03-17 12:19:44.027175: [TUN] [nm-mat] Interface created
2022-03-17 12:19:44.192576: [TUN] [nm-mat] Dropping privileges
2022-03-17 12:19:44.192576: [TUN] [nm-mat] Setting interface configuration
2022-03-17 12:19:44.194576: [TUN] [nm-mat] Unable to bring up adapter: The process cannot access the file because it is being used by another process.
2022-03-17 12:19:44.193574: [TUN] [nm-mat] Peer 2 created
2022-03-17 12:19:44.193574: [TUN] [nm-mat] Peer 3 created
2022-03-17 12:19:44.193574: [TUN] [nm-mat] Peer 4 created
2022-03-17 12:19:44.194576: [TUN] [nm-mat] Peer 5 created
2022-03-17 12:19:44.194576: [TUN] [nm-mat] Peer 6 created
2022-03-17 12:19:44.194576: [TUN] [nm-mat] Peer 7 created
2022-03-17 12:19:44.194576: [TUN] [nm-mat] Could not bind socket to [::]:51821 (0xc0000043)
2022-03-17 12:19:44.445290: [TUN] [nm-mat] Shutting down

handsome-lifeguard-70799

03/17/2022, 12:22 PM

Might just be reboots needed at this point, which I can't do right now

handsome-lifeguard-70799

03/17/2022, 12:23 PM

No just in the metadata of the binary, also shown when you hover over it

handsome-lifeguard-70799

03/17/2022, 12:25 PM

I'd better get back to this proposal that needs to be finished today, but will update later once our team are offline

few-airline-95046

03/17/2022, 1:07 PM

I noticed the 0.8.5 version as well when I wanted to verify which binary was run and checked using

Get-Command netclient

handsome-lifeguard-70799

03/18/2022, 11:23 AM

Morning - a reboot sorted my windows 2016 server out, so the directly downloaded binary does work with all peers showing today in wg show, but no joy with the PowerShell download still