Simple Multi-cloud deployment - Routers Configuration

[plorenz]

@arslane

the only difference is that Fabric has link.listeners only, Private has only listenersand Edge routers has both.
What I’m understanding by comparing those two config files is that :

• link.listeners is used to tell the router “Hey, listen on traffic coming from outside of the Ziti Overlay”
• listeners tells the router “Hey, listen on traffic coming from inside of the Ziti Overlay”

I’m not really confident when saying this, because it kinda looks wrong, I mean, why does a Fabric router should be routing traffic coming from outside ? Isn’t that the job of an Edge router ?

Close, but backwards

Links are what connect routers to each other. So a router with link.listeners can receive connections from other routers to form the mesh. Routers that have link.dialers configured will try to make connections with routers that have a link.listeners configured. A router can have both dialers and listeners configured.

Every router, fabric or edge, should generally participate in the mesh, so usually every router will have either link.dialers and/or link.listeners configured.

The listeners section is for configuring components which can feed external traffic into the ziti fabric or sent traffic out of the fabric. Generally this means the edge. If you want to enable edge functionality, you need to specify an listeners section for edge, as well as a top level edge: section. If you want to use the combined edge router/tunneler, you also need a listeners section for the tunnel.

Example:

listeners:
  - binding: tunnel
    options:
        mode: host
  - binding: edge
    address: tls:0.0.0.0:7876
    options:
      advertise: 127.0.0.1:7876

Hope that's helpful, let me know if I can provide more details.
Cheers,
Paul