Just to be absolutely clear, you are meaning on the two devices I have connected to the ZT network that are (supposed to be) routing between my private IP spaces and ZT? I tried that setting and it did not seem to make any difference.
I did notice one other extremely odd behavior (ie I don’t understand it at all). Here is a traceroute from the test node on Site A (172.16.1.0) to the main router located at Site B (192.168.50.0)
$ traceroute 192.168.50.1
traceroute to 192.168.50.1 (192.168.50.1), 30 hops max, 60 byte packets
1 172.16.1.13 (172.16.1.13) 0.234 ms 0.215 ms 0.203 ms
2 172.30.0.14 (172.30.0.14) 6.907 ms 6.929 ms 6.943 ms
3 192.168.50.1 (192.168.50.1) 7.256 ms 7.272 ms 7.290 ms
$
The trace correctly gets the ZT gateway from the Site A router (ie 172.16.1.13), then traverses the ZT network to the gateway on the Site B network (ZT IP 172.30.14) and thence to the target… Looking good.
If I repeat the same test except targeting a different node on the Site B network, eg 192.168.50.250, I get a single hop to the Site A router, and then the traceroute ends - almost like something in the Site A router config is not quite right.
ie
$ traceroute 192.168.50.250
traceroute to 192.168.50.250 (192.168.50.250), 30 hops max, 60 byte packets
1 172.16.1.1 (172.16.1.1) 0.299 ms 0.265 ms 0.205 ms
$
What is confusing me here, and is almost certainly my lack of understanding of network topology is that pinging from Site B hosts to Site A hosts works perfectly fine, so there is definitely some route back.