plus a lot of times issues can be fixed by just restarting the containers

but there's nothing wrong with installing natively on the machine either

if that's what you prefer

Understand

Hi, I'm having an odd issue with a Windows client. I can ping most of the peers and the Netmaker hub however 1 peer I am unable to reach, I get nothing back from a ping and unable to connect to services on the peer. Other clients ( Linux ) are able to reach all peers. Any ideas?

might be an issue with MTU; try lowering it on the windows client

ah ok, any suggested values?

Currently set to 1280 which matches the MTU for the TailScale interface ( BTW I'm testing NetMaker to replace TailScale )

seems to be popular use case

Yeah I noticed that 🙂

@miniature-plumber-58921 I've been using 1450 for my windows clients at the suggestion of @jolly-london-20127 , I think it was. Seemingly working well. Also make sure you have firewall rules as per the powershell command in the docs. I edited for my whole Netmaker range instead of a single IP. Sometimes Windows clients need a couple of pulls, and a checkin doesn't hurt for good measure. They used to need rebooting on earlier client versions, but that has been addressed now for a few versions. Only other thing I can suggest checking again is if you have multiple machines behind one NAT then you need to forward to different ports, check both router and UI, or use UDP hole punching.

Hey guys, just wondering if a) we are able to configure a windows node as an egress and b) how to format the interface name if you can

egress nodes are limited to linux at the present time

Ok thanks 👍

Just a note that windows defender is at it again, says that netclient.exe file is a virus when running autoinstall script

Bitdefender kills off the netclient.exe from the service location too

Windows node is making a weird thing, where it stops responding to pings from certain (but not all) other clients from the network for an hour or so. I don't know if it is the windows behavior or something with netmaker network and/or clients

if noticed random ping interruptions on windows as well, really not sure where those come from at this point

Interestingly enough, I tried pinging public ip instead, as it still has a client-facing service running, and it seems to be a-ok with ping response 100%. My windows firewall rule for netmaker is to allow x.x.x.0/24 (nm-network ips)

just got v0.11.0 up and running. Only issue so far is none of the windows clients can pull. Just hangs on`Gravitl Netclient on Windows started`

Have to reboot to pick up changes

Hmmm, windows clients seem a bit broken right now. Not picking up changes at all, hanging trying to manually join with tokens

Hangs... seems like netclient can no longer reset the wireguard interface. Tried five different machines in 3 different locations.

netmaker logs:

Do you try on linux machine (without docker) ? Maybe i can try later to add my windows machine to my network for testing ;)

@User yes, linux all working perfectly

feels a bit like the v0.8 days with regards to windows clients not being able to reset the WG interface properly. pull is just not working anywhere and reboots are hit and miss

No one else?