Firstly my apologies to @mlavelle42 - I didn’t mean to not answer your question; I never received any notification of it.
@higgssinglet - IIRC (and I’ll post again in the next couple of days once I’ve confirmed; I no longer have a test lab for ZT) once the GL.iNet router is connected to ZT and has an IP address you need to do the following on the router:
- Change the GL.iNet FW in LuCI (advanced settings) to allow traffic to flow. I think here I simply added the ZT interface to the LAN Zone.
- I also added in / changed specific firewall rules to allow at least an IPv4 Ping (ICMP echo) to traverse the GL.iNet router. This is mostly for testing and can be reverted afterwards.
Note you don’t want the ZT interface on the GL.iNet to have NAT (Mascarade). If you do it will appear to work but it things will only work in one direction - from GL.iNet to ZT devices.
Then from Networks in ZT Central (my.zerotier.com/networks/[networkID] where [networkID] is the 16 digit number eg my.zerotier.com/networks/35d532de5b267e8a) you need to add a managed route (very top right of the interface).
For the network add your GL.iNet IP address range (so 192.168.8.0/24 by default) in the box marked Network/Bits and then add in the routers ZT interface IP address into the (LAN) box. This (LAN) IP can be found as Managed IP in the Members section of the Network Page for your GL.iNet device (about 1/2 way down). For the avoidance of doubt this is not the physical IP.
So if your GL.iNet router is assigned 10.147.0.53 by ZT and your router’s still at the default it will look like this:
And that’s it, all the devices that are then attached to the LAN of your GL.iNet (i.e those that have a 192.168.8. prefix to their IP address) will be able to communicate with any other ZT device. All your really doing is adding a static route to ZT’s routing table.
(and yes I agree that ZT should have used standard networking terminology for things like managed router and managed IP as well as keeping the naming conventions consistent!)