| Interconnect seam | Served LAN | Subnet router on a flat overlay |
| The other side | Members of another Atlas network, run by its own operator | A plain LAN whose hosts run nothing, behind a node of your own network | A plain LAN whose hosts run nothing, behind a device of the overlay |
| Who configures | The seam host only: each operator writes its own export list, map entries and routes for its own daemon. Members configure nothing | The serving node only: one [[serve]] block. Members keep the default; the LAN needs nothing, or one static route on its gateway | The router advertises the prefix, an administrator of the overlay approves it in most designs, and some clients opt in to accept it |
| Addresses | Mapped mode: a far host appears at an address you choose inside your own subnet, and the sender appears at its mapped address on the far side. Prefix mode: real addresses both ways, nothing rewritten | Members reach the LAN’s hosts at their real addresses. With masquerade on, the default, the LAN sees the serving node; off, with the gateway route, real addresses both ways | Devices reach the LAN’s hosts at their real addresses. By default the router translates the source, so the LAN sees the router; the real source needs a return route on the LAN |
| Direction | Both ways, for the hosts on each side’s export list; in prefix mode each direction crosses only when one side’s route and the other side’s export both list it | Mesh to LAN, for the sources the for list names. LAN to mesh as well with masquerade off and the gateway route | Overlay to LAN. LAN to overlay where source translation is off and the return route is in place |
| Route origin | The seam daemon. Mapped mode: it serves each mapped address inside the subnet members already route. Prefix mode: it imports the far prefix and advertises it in its network’s signed link-state adverts | The serving node floods the prefix in its signed advert, and every member’s daemon installs it on its own tunnel interface; in a record fleet the node’s record bounds what it may serve | The coordination service distributes the approved route to the overlay’s devices |
| Trust domains | Two networks, each with its own keys, admission and operator; the seam host is a member of both, and either side ends the join by revoking it | One network; the serving node is one of its members | One overlay: one coordination service, one policy, one set of administrators |
| Failover | Two seam hosts serving the same addresses: the other takes over within seconds, in both modes | Two nodes serving the same LAN: each member uses the nearest, and traffic moves within seconds when one goes away | Several routers can usually advertise the same prefix |
| Path | Always through the seam host; on each side, that network’s own routed paths and bonded links | The mesh’s own routed paths, across as many hops and bonded links as the topology takes | Direct between devices where NAT allows, else through a relay; LAN traffic goes through the router |