[Bug]: Netclient in Windows 10

gravitl / netmaker

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

https://netmaker.io

Other

9.36k stars 544 forks source link

[Bug]: Netclient in Windows 10 #1471

Open squromiv opened 2 years ago

squromiv commented 2 years ago

Contact Details

github

What happened?

Graph screenshot 2022-08-21 02-38-31 001 Netmaker dashboard: screenshot 2022-08-21 02-40-37 001 node2 status: screenshot 2022-08-21 02-42-39 001 node2 Wireguard app log: screenshot 2022-08-21 02-53-53 001

node2 Wireguard fails to complete handshake with node1. IP of node2 is not changing to IP of netmaker-1 node despite its ingress and egress status. ext1 is able to connect to node1 and node2.

Have tested node2 Wireguard with other vpn service, works as it should.

Version

v0.14.6 Wireguard v.0.5.3

What OS are you using?

Windows 10 Home

Relevant log output

No response

Contributing guidelines

[X] Yes, I did.

afeiszli commented 2 years ago

have you run a "pull" on the netclient?
is udp hole punching on?

squromiv commented 2 years ago

have you run a "pull" on the netclient?

screenshot 2022-08-27 12-31-12 001

2. is udp hole punching on?

screenshot 2022-08-27 12-31-54 001

afeiszli commented 2 years ago

Oh! I just realized you are using 0.0.0.0/0 as an egress gateway. If you check the release notes from 0.15.0, this is just now supported. In our docs, we note in previous versions that 0.0.0.0/0 will not work.

This is because routes need to be configured for the client to reach the other clients. Otherwise, it tries to reach them over the internet gateway, which will not work because there is no route to reach the internet gateway.

Please upgrade to 0.15.0 and try again.