Mon May 02, 2022 6:05 pm
The ZT Interface selector on the instance controls where it will establish tunnels to other ZT peers/etc. May not 100% accurate but essentially "instance" (e.g. "zt1") is what establishes ZT tunnels, the get manifests as ZT network interface ("zeroteir1").
By default ZT will attempt to establish a connection on "all" interface, since you may have peers on the LAN and WAN at same time. But if you pick an interface[/list], then it will ONLY use that to establish tunnels.
If you goal is remote access to the router itself, then could use "WAN" (or your uplink interface). Now if the interface[/list] has no direct internet access, like "LAN", it might be a problem since it might be restricted from reaching the root/planets.
I've just left it "all", but I can see use cases ZT network or security model where you would rather not have all the ZT stuff going doing some interface.
You can try different settings, and the effects can be seen in the "Peer" view. You may have to click on a particular peer to see the full list of "Paths" - winbox's list only shows the first one.