I currently face the issue, that if I have an existing route to a zerotier allocated IP and then change that route, the MacOS client does not reflect that change unless disconnected and reconnected, at which point the route change is there immediately.
Example:
1.2.3.4/28 → 172.25.1.1
change to:
1.2.3.4/28 → 172.25.1.2
validate with route get 1.2.3.4/28 → shows old next hop unless reconnected
We run a setup where devices register themselves to the zerotier network and expose their local networks as routes. So whenever that happens this case can potentially occur. Specifically local networks are auto allocated too, so they might be relinquished again after a while and then another node can export it again which leads to exactly that case.