New install
# installw
white-smartphone-70691
03/20/2023, 5:25 PMFirst time install of Netmaker. I've previously used ZeroTier & Tailscale successfully, but want to switch a a control plane under my control. I installed the NM server on a newly-created VPS, and everything appeared to work fine. I've installed five NM clients (one MacOS & four Debian)--all are behind a router, all appeared to install correctly and all indicated a status of "healthy" on the NM dashboard immediately upon installation. I'm currently experiencing the following connectivity problems: (1) the four Debian clients can each ping the NM server by either name or IP address, but cannot ping each other using either the name or IP addresses (/etc/hosts on each correctly contains names/IP addresses). (2) the MacOS client can ping the NM server by IP address only ('ping: cannot resolve netmaker-1.wg-nm: Unknown host' when attempting to ping by name). (NOTE: /etc/hosts is not updated by NM on the MacOS client either). (3) finally, the status of the MacOS machine on the NM dashboard changes from 'healthy' to 'warning' after a few minutes, and finally changes to 'error'. Even after the status changes to 'error' on the dashboard the MacOS machine can still ping the NM server by IP.
b
bored-island-21407
03/20/2023, 5:28 PMWhat version did you install,,?
w
white-smartphone-70691
03/20/2023, 5:29 PMv0.17.1 on everything (just installed this morning)
b
bored-island-21407
03/20/2023, 5:30 PMare the debian hosts behind the same router?
bored-island-21407
03/20/2023, 5:31 PMthe warning/error status for the Mac indicates it is not connecting with the server over MQ so it will not get any updates
w
white-smartphone-70691
03/20/2023, 5:31 PMthe mac & debian hosts are all behind the same router. the NM server is on a vultr.com VPS running Ubuntu (per the quick install script)
white-smartphone-70691
03/20/2023, 5:35 PMtried turning off 'UDP hole punching' on the server, and now the debian clients can ping each other (and I can ssh between them, as well). so, that seems to be part of the problem.
b
bored-island-21407
03/20/2023, 5:35 PMv0.17.x and earlier has a problem with nodes behind the same router.... v0.18.x does it bit better
w
white-smartphone-70691
03/20/2023, 5:39 PMi did install on the mac using 'homebrew'--I may try it again with a manual install
white-smartphone-70691
03/20/2023, 5:40 PMdo you have any idea why the 'UDP hole punching' made a difference with the debian clients? the installation instructions had recommended turning it on to help with clients located behind NAT--it seemed to have the opposite effect.
b
bored-island-21407
03/20/2023, 5:46 PMUDP holepunching will change which port each client is listening on
w
white-smartphone-70691
03/20/2023, 5:48 PMuninstalled the client from the mac, and reinstalled using the 'pkg' from github (rather than using homebrew to install). as soon as I reinstalled, the mac came up as 'healthy' (I didn't even need to rejoin the network).
white-smartphone-70691
03/20/2023, 5:49 PMI can now ping any other client via name or IP address from the mac. I can also ssh to the debian machines from the mac. now, /etc/hosts on the mac is being updated.
white-smartphone-70691
03/20/2023, 6:00 PMlogged into the VPS host containing the server. ran:
white-smartphone-70691
03/20/2023, 6:00 PMfor x in 11 12 13 14 24 ; do docker exec -it netmaker ping -c 2 10.11.12.${x}; done
white-smartphone-70691
03/20/2023, 6:01 PMand received a pong from all clients. Seems all my initial issues are corrected. @bored-island-21407 thanks for letting me bounce this off of you!
b
bored-island-21407
03/20/2023, 6:02 PMNP