Connection drops on mikrotik

Community Support Linux
, ,
1

Hi guys,
I have Zerotier installed on my Mikrotik router that is connected to a server (direct connection) from another place and there is also a static route configured so from Mikrotik I can access all devices within that Server network and vice-versa from Server to Mikrotik Lan network.

I noticed however that sometimes the connection becomes unstable where the ping goes from normal <20ms to >10000ms while I ping the Server from my Raspberry Pi, If I ping from Mikrotik router or windows, it simply return connection timeout.

I noticed this in particular when I have hosted a monitoring network (uptime-kuma) where it does ping many devices within ZT Server network once a minute to check uptime otherwise send an alert. I’m starting to think that ZT somehow on many ICMP packets is having trouble here and I’m trying to understand how to fix that, if anyone had this similar issue and found a solution, I’d really appreciate it.

The monitoring is hosted on Pi, but if Raspberry Pi send those packets on vpn, also access from other devices, either router Mikrotik, or windows computer stops working for a few minutes, not only from Pi.

[Ping from Pi to Server that host ZT]
64 bytes from 192.168.10.10: icmp_seq=1727 ttl=62 time=9.12 ms
64 bytes from 192.168.10.10: icmp_seq=1728 ttl=62 time=9.13 ms
64 bytes from 192.168.10.10: icmp_seq=1729 ttl=62 time=8.88 ms
64 bytes from 192.168.10.10: icmp_seq=1730 ttl=62 time=9.46 ms
64 bytes from 192.168.10.10: icmp_seq=1731 ttl=62 time=8.71 ms
64 bytes from 192.168.10.10: icmp_seq=1732 ttl=62 time=9.04 ms
64 bytes from 192.168.10.10: icmp_seq=1733 ttl=62 time=11.0 ms
64 bytes from 192.168.10.10: icmp_seq=1734 ttl=62 time=8.77 ms
64 bytes from 192.168.10.10: icmp_seq=1735 ttl=62 time=8.97 ms
64 bytes from 192.168.10.10: icmp_seq=1736 ttl=62 time=9.69 ms
64 bytes from 192.168.10.10: icmp_seq=1737 ttl=62 time=3442 ms
64 bytes from 192.168.10.10: icmp_seq=1740 ttl=62 time=12280 ms
64 bytes from 192.168.10.10: icmp_seq=1741 ttl=62 time=11279 ms
64 bytes from 192.168.10.10: icmp_seq=1742 ttl=62 time=10265 ms
64 bytes from 192.168.10.10: icmp_seq=1743 ttl=62 time=12236 ms
64 bytes from 192.168.10.10: icmp_seq=1744 ttl=62 time=14213 ms
64 bytes from 192.168.10.10: icmp_seq=1745 ttl=62 time=13189 ms
64 bytes from 192.168.10.10: icmp_seq=1746 ttl=62 time=12165 ms
64 bytes from 192.168.10.10: icmp_seq=1747 ttl=62 time=11141 ms
64 bytes from 192.168.10.10: icmp_seq=1748 ttl=62 time=10118 ms
64 bytes from 192.168.10.10: icmp_seq=1749 ttl=62 time=9094 ms
64 bytes from 192.168.10.10: icmp_seq=1750 ttl=62 time=8070 ms
64 bytes from 192.168.10.10: icmp_seq=1751 ttl=62 time=13050 ms
64 bytes from 192.168.10.10: icmp_seq=1752 ttl=62 time=12027 ms
64 bytes from 192.168.10.10: icmp_seq=1753 ttl=62 time=11026 ms
64 bytes from 192.168.10.10: icmp_seq=1754 ttl=62 time=10011 ms
64 bytes from 192.168.10.10: icmp_seq=1755 ttl=62 time=9008 ms
64 bytes from 192.168.10.10: icmp_seq=1756 ttl=62 time=7996 ms
64 bytes from 192.168.10.10: icmp_seq=1757 ttl=62 time=6972 ms
64 bytes from 192.168.10.10: icmp_seq=1758 ttl=62 time=5973 ms
64 bytes from 192.168.10.10: icmp_seq=1759 ttl=62 time=4957 ms
64 bytes from 192.168.10.10: icmp_seq=1760 ttl=62 time=3933 ms
64 bytes from 192.168.10.10: icmp_seq=1761 ttl=62 time=2910 ms
64 bytes from 192.168.10.10: icmp_seq=1762 ttl=62 time=1886 ms
64 bytes from 192.168.10.10: icmp_seq=1763 ttl=62 time=870 ms

2

Zerotier latest version for mikrotik is 1.10.3 while latest version of zerotier for other devices is 1.10.6.
Since version 1.10.6 came out my mikrotik’s zerotier connection became unstable.
I guess mikrotik has to upgrade zerotier package to 1.10.6 to solve our issue. Let’s hope this time won’t take a whole year for mikrotik to update their zerotier package as before

3

True, version for Mikrotik is 1.10.3, Checking the changelog for zerotier, I wouldn’t say this could be the cause.
Now, if Mikrotik is slow at updating apps, like we will finally receive version 1.10.6 and short after Zerotier updates to 1.10.7 and we’re still here on old version.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.