Secondary ip and binding

Hi guys, I’m having to issues and I might be missing something very basic:
Bottom line: I have an ethernet interface 10.1.100.160, a ZT interface 10.147.18.16 and I added another IP to it (from TZ’s web interface) 10.10.0.254

  1. I cannot seem to ping a host connected to the ethernet interface with the ip of 10.10.0.1 (its defalut gateway is 10.10.0.254)
  2. I cannot ping it from that same PC even with -S (source) being 10.10.0.254
    The ZT interface was suppose to communicate with the ethernet one, right ? (i tried enabling ‘allow ethernet binding’ - still the same
  3. at some poing my ZT interface stopped receiving the 2nd IP (10.10.0.254) - and no matter what I do - it does not come back. Why?
  4. Does the ZT cloud learn the routing by itself (so that the my cloud no knows that 10.10.0.0/C is behind 10.147.18.16) Or should I add it in the routes section?
    Thanks

Did you bridge the interfaces?

You going to need “Essential” account to manage routes.
If you do, go to ZT dashboard and make your routes

For your scenario, it would be something like

Destination → 10.10.0.0/24 Via → 10.1.100.160
Destination → 10.147.18.0/24 Via → 10.1.100.160

Adjust the network size as you need.

In my case I’m using a /16 ZT network.