Had to reboot a Synology in one of our offices (we have 3 locations with same Synology RS and ZT dockered on all of them, version 1.10.6)
After the reboot the ping from any other ZT client shows:
PING 172.26.100.5 (172.26.100.5) 56(84) bytes of data.
64 bytes from 172.26.100.5: icmp_seq=1 ttl=64 time=14.7 ms
64 bytes from 172.26.100.5: icmp_seq=1 ttl=64 time=14.7 ms (DUP!)
64 bytes from 172.26.100.5: icmp_seq=2 ttl=64 time=6.10 ms
64 bytes from 172.26.100.5: icmp_seq=2 ttl=64 time=6.15 ms (DUP!)
To any other Synology on same ZT network/version/router etc it works fine:
PING 172.26.100.7 (172.26.100.7) 56(84) bytes of data.
64 bytes from 172.26.100.7: icmp_seq=1 ttl=64 time=18.3 ms
64 bytes from 172.26.100.7: icmp_seq=2 ttl=64 time=8.33 ms
64 bytes from 172.26.100.7: icmp_seq=3 ttl=64 time=8.68 ms
100% positive this wasn’t before the reboot but it seems weird a reboot can cause this, right?
ZT is not tunneled as far as I can see from zerotier-cli info on the Synology.
Any ideas why and how to solve? Will this impact performance (hard to see now on a weekend, but if this causes issues on Monday I’m toast.
We have a Professional account btw