Ziti-tunnel.resolver.test

Ahhh, yeah. I forgot you were running it in a VM and that VM has a different IP address. You got it right... You should change your hosts file though. you probably want just one line:

192.168.188.134 ziti-edge-controller ziti-edge-router

The ziti-edge-router needs to be addressable too from your ZDEW or else traffic won't flow! :slight_smile:

You can check that advertised address with something like:

$ docker compose exec ziti-edge-router grep -B2 -A2 advertise ziti-edge-router.yaml
    - binding:          transport
      bind:             tls:0.0.0.0:10080
      advertise:        tls:ziti-edge-router:10080
      options:
        outQueueSize:   4
--
    address: tls:0.0.0.0:3022
    options:
      advertise: ziti-edge-router:3022
      connectTimeoutMs: 5000
      getSessionTimeout: 60

So this is showing you that other routers will try to connect to this router at: tls:ziti-edge-router:10080 and edge devices will try to connect to the edge (data) plane at ziti-edge-router:3022

So make sure your ZDEW can connect to that port too! We always recommend using/learinging openssl s_client -connect to test that port:

openssl s_client -connect ziti-edge-router:3022

make sure you see "stuff" coming back. For example at the end you should see:

Verify return code: 20 (unable to get local issuer certificate)