Zerotier router setup not working

I’ve followed the basic setup for the router: Set Up a ZeroTier Network on OpenWRT • KEVRON2u.COM by KEVRON Enterprise

And everything seems to be in order, I have authenticated my router in the zerotier homepage and If I call on the status it’s online, as shown below.

root@pcwrt:~# zerotier-cli info
200 info d0xxxxxxx 1.6.5 ONLINE

Now, whatever device I connect to my router I want it to get a ZeroTier IP-adress. That was the purpose of the whole thing. I suspect my ‘Manage routes’ needs changing but I’m getting nowhere.
I currently have it set to this. My other device connected to router still gets 192.168.10.XXX IP. What is wrong?

Managed Routes VIA (LAN)

ZeroTier IP =
Router homepage =

With the configuration example you mentioned only your router supposed to receive the address from the ZeroTier network.
Until you have a very specific use case in mind, your LAN devices do not need to obtain new addresses. If you have some devices behind 2 or more routers (acting as ZT clients) and you want them to communicate over ZeroTier network you will need to configure the routes on the Controller and setup the firewall rules on your routers.

I am trying to reach Because I have ZeroTier on the router it’s connected to I am trying to configure settings so that can reach that from my laptop which is running ZeroTier but from another network/away from home. I thought that the connected LAN devices to the ZeroTier router would automatically get assigned an ZeroTier IP that I could reach but seems I was wrong.

But I don’t know how to setup ‘Manage Routes’ correctly to achieve that.
How do I connect to from another network?

Think of ZeroTier network as a generic router.
What you have is something like this:
LAN1–R1—R3–R2–LAN2 or LAN1–R1—R3–PC
R1 (and R2) is your router. R3 is Zerotier.

“Managed Routes” is equivalent of the static route configured on R3:
LAN1 ( is reachable via “R1 ZT address”
LAN2 (…) is reachable via “R2 ZT address”

Once configured these routes will be automatically propagated to all the ZT network members like routers and standalone PCs.

So the wiki page is missing information?

Because according to that, all that would be needed is:
$PHY_SUB via $ZT_ADDR (in my case: via

Along with the added iptables rules and enable ipv4 forward for everything to work?

Some minor changes. Like “-m state --state” to “-m conntrack --ctstate” in order for OpenWRT to accept the commands. And iptables are written at boot in another way because iptables-persistent doesn’t exist. Apart from that, I’ve followed the wiki page exactly like its written.

This wiki page is irrelevant if you use OpenWrt.
If you having difficulty setting up OpenWrt firewall I suggest to ask a question in OpenWrt forum.

@Aland0, that link is used only if you want to install ZT on an independent node in the network and not directly in the router itself. In your case, all traffic to the ZT network is handled by OpenWRT and there is no need to install ZT on the individual LAN devices.

From your LAN (192.168.10), try to ping any zt device on the 10.144.223 network. If that succeeds then everything is ok, otherwise you need to look over the routing table in OpenWRT and make sure there is a route to the ZT network that looks something like this:

Destination   Gateway  Genmask        Flags Metric Iface  U     0      zt7nniznus

Btw, if possible use /23 in “Managed Routes”, ie “ VIA”. The reason for this is explained in the link.

Needs correction, otherwise OP will be confused :wink:

1 Like

But hey, good catch!

And you possibly also found the root cause of the problem itself, i.e. Managed Routes that were specified in the first post as “ VIA” should have been the other way around ie. “192.168.10/23 VIA

1 Like

I made it work. The setup was easy in the end. Everything was sorta correct but in reverse order. /24 is currently working though, i haven’t tried /23

Managed Routes 2/128 (LAN) via

This was all that I was after from the beginning, just the right configuration.

1 Like

Yes that was the problem, i got it working in the end. I was on the right track but the Managed Routes were in the wrong order (other way around).

1 Like

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