search

gravitl / netmaker

Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
https://netmaker.io
Other
9.5k stars 552 forks source link

[Bug]: Windows Netclient, server can't ping win client, but the win client can ping server #1594

Open MatthewReed303 opened 2 years ago

MatthewReed303 commented 2 years ago

Contact Details

No response

What happened?

I have tested this on 3x different win10 PCs running v0.16.0 netclient. I can not ping any of the win10 netclients from the netmaker server. All the clients can ping the Netmaker server. None of the win10 clients can ping each other. With my 2x Linux Netclients I can ping between the linux clients and the win10 client can reach the linux clients but just not vice versa.

win10client --------> NM-Server OK NM-Server --------> win10client BAD win10client -------> linuxClient OK linuxClient --------> win10client BAD linuxClient --------> linuxClient OK

Version

v0.16.0

What OS are you using?

Windows

Relevant log output

No response

Contributing guidelines

afeiszli commented 2 years ago

This is probably just your Windows firewall. I believe ping (ICMP) is often disabled on Windows.

https://ccm.net/computing/networks/1629-what-to-do-when-you-re-unable-to-ping-a-computer-on-the-same-network/

MatthewReed303 commented 2 years ago

I did check windows firewall and ICMPv4 is enabled for all machine, but still not working. In the end I created new custom rule for ICMP for the windows PCs and I can now ping them all from the server and vice versa. ( I never had this issue with v14.6 ) I still can't ping between clients so there is still an issue somewhere or routing issue. I have done new pulls etc and still no luck.

win10client ---------->NM-Server OK NM-Server ----------> win10client OK win10client ---------> win10client BAD

MatthewReed303 commented 2 years ago

I think I have solved the issue... It's the UDP hole punching causing issues, if I switch it off everything works as expected. I don't understand how this affects connection between the clients, I thought it is used to establish connection with the server. I have been mucking around with UDP hole punching on and no matter what I try I can't get the windows clients to ping each other.

I have tried changing the tunnel interface to private ( they automatically get set to public ) have disabled windows firewall ( domain/private/public ) for both clients and still no luck.

Hopefully I won't need UDP hole punching for my 4G LTE connections, I will get some sim cards next week and do some testing. If my server is hosted on a VPS with public IP is UDP hole punching needed?

abhishek9686 commented 5 months ago

I think I have solved the issue... It's the UDP hole punching causing issues, if I switch it off everything works as expected. I don't understand how this affects connection between the clients, I thought it is used to establish connection with the server. I have been mucking around with UDP hole punching on and no matter what I try I can't get the windows clients to ping each other.

I have tried changing the tunnel interface to private ( they automatically get set to public ) have disabled windows firewall ( domain/private/public ) for both clients and still no luck.

Hopefully I won't need UDP hole punching for my 4G LTE connections, I will get some sim cards next week and do some testing. If my server is hosted on a VPS with public IP is UDP hole punching needed?

can you try your setup with the latest version?