Interconnect over relays

Networks over the relays.

The traversal network carries more than one node talking to another. A node that serves a site’s LAN, a host that joins two Atlas networks, an exit to the internet: each is an ordinary member with relay links, so what it brings in reaches the rest of the fleet across carrier NAT, with no public address anywhere.

Building blocks

One network extended, or two networks joined.

Each block is configured on one node only. Every other member learns what it needs from the signed adverts that already carry the network’s routing, whichever path, relayed or direct, carries the session.

NATCarrier NAT CameraPLCServer GatewayRelayFleet node a plain LAN serves the /24 learns the route hosts that run nothing, reached at their own addresses
One block on the gateway serves the LAN. The fleet node reaches its hosts over whatever carries the session: a relay, a federated pair or a direct path.
MemberMember AB MemberMember Network ANetwork B seam hostlocal link each daemon reaches its own members over its own relays
One host, one daemon per network. Adverts, gossip and keys stop at the seam; only traffic between exported hosts crosses.
Served LAN

A plain LAN, served into one network

A node with an interface on a site’s LAN serves its prefix with one [[serve]] block. Printers, cameras, controllers and servers on it run nothing. Every member installs the route from the serving node’s signed advert and reaches each host at its own address; with masquerade on, the LAN sees the serving node, and with one static route on the LAN’s gateway, real addresses both ways. for names who may cross, and two serving nodes fail over within seconds.

Interconnect seam

Two Atlas networks, joined at one host

A host that is a member of both networks runs one daemon for each, joined by a link that exists only inside that host. Mapped mode shows a far host at an address inside your own subnet; prefix mode routes the other network’s members at their real addresses. Export lists on both sides gate both directions, nothing chains through to a third network, and in a fleet run from signed records the seam host’s record limits what it may import and export.

Exit

The internet, as the far end

A hosted exit on every relay host, or a private exit with one [exit] section on a node you run. The device’s whole default route goes into the tunnel, and the internet sees the exit’s address.

A served LAN never crosses an Interconnect seam: a served prefix lies outside the network’s own subnet and a seam exports only addresses inside it. Payloads sealed end to end are opened and re-sealed at a seam host, and served-LAN traffic leaves the tunnel at the serving node as plain IP on the LAN. Who holds the keys on each path

Nexus Atlas: Interconnect3:34 · plays from YouTube
Scenarios

Five ways a network crosses the relays.

Each scenario names what sits on each side, which relay mode carries it, the configuration sections involved and what the people using it get.

01 · A gateway’s /24 to a fleet node

A site gateway serves its LAN to a node of the fleet, over the relay.

A site with no public address has a flat /24 of cameras, controllers and a file server. One Linux node sits at the site boundary with an interface on that LAN. A fleet node, a vehicle or a ground station on cellular, needs to reach those hosts.

On one side
The gateway node behind the site’s NAT, with its LAN interface on 192.168.10.0/24. Nothing on the LAN runs Atlas.
On the other
A fleet node behind carrier NAT, member of the same network.
Carried by
A shared relay or a federated pair; a direct path when both NATs allow it, with the relay on standby.
Configured
On the gateway, [[serve]] (prefix, interface, masquerade, for) beside [traversal] and its relay link; on the fleet node, [traversal] only. Members keep [routing] install_learned_routes at its default.
What you get
The fleet node reaches the camera at 192.168.10.50, its own address, through the relay. With masquerade off and one static route on the site’s gateway, the file server opens connections back to the fleet node’s tunnel address.
02 · Two fleets, one seam

Two fleets join at a seam, each reaching it over its own relays.

Your operations network and a partner’s drone network each have their own operator, keys and addresses, and their members sit behind whatever NAT their bearers bring. Neither will merge into the other. Join two networks, merge neither.

On one side
Network A, your members, homed on the relays near them.
On the other
Network B, the partner’s members, homed on theirs.
The seam
One host admitted to both networks, running one daemon per network, the two joined by a loopback-only [[link]] of type local.
Carried by
On each side, that network’s own shared relays, federated pairs or direct paths between its members and its daemon on the seam host; across the seam, the link inside the host.
Configured
On the seam host only: [peer.interconnect] with its export list, [[peer.interconnect.map]] for mapped hosts, [[peer.interconnect.route]] for whole prefixes. In a record fleet, the seam host’s signed record carries what it may import and export.
What you get
Your members reach the partner’s camera at an address inside your own subnet, or its whole ground-control prefix at real addresses. Neither network learns the other’s topology; either operator ends the join by revoking the seam host; a route outside the record is refused by every member on its own.
03 · A depot over cellular

A vehicle fleet reaches its depot’s LAN over carrier NAT.

Vehicles on cellular change towers, carriers and addresses all day. The depot behind a broadband router keeps a dispatch server and maintenance machines on its LAN that run nothing but their own software.

At the depot
A node on the depot LAN serving its prefix; a second node can serve the same LAN and take over within seconds.
On the road
Vehicles behind carrier NAT, each homed on a relay near it, two relay paths active.
Carried by
Shared relays or federated pairs. A vehicle whose carrier mints a new port per destination stays relayed; one whose carrier keeps one mapping gains a direct path to the depot.
Configured
Depot nodes: [[serve]], with for naming the vehicles allowed in. Vehicles: [traversal] with auto_relay and relay_paths; a [policy] rule can hold relayed links as standby or keep a traffic class off them.
What you get
Every vehicle reaches the depot’s hosts at their own addresses through each handover, and refusals from any other source are counted at the depot node. With masquerade off and one route on the depot’s gateway, dispatch opens connections to the vehicles.
04 · Ground station to operations

A drone’s ground station behind one NAT, the operations centre behind another.

The ground station runs on cellular or satellite in the field; the drone is a member over its radio link to the ground station; the operations centre sits behind an office firewall on another continent.

In the field
The ground station homed on its nearest relay; the drone reached over its radio link; a camera on the drone’s own Ethernet served into the mesh by the drone’s node.
At operations
Consoles behind the office NAT, homed on the relay nearest them. Outbound only.
Carried by
Federated relays, each end on its nearest; a direct path when both NATs allow it, with the relays as the fallback.
Configured
[traversal] with federation at the ground station and at operations; [crypto] e2e on every node involved, which a federated path requires; [[serve]] on the drone’s node for its camera LAN.
What you get
Operations reaches the drone and its camera at their own addresses: across the relays to the ground station, then across the radio link. With end-to-end sealing on, neither the relays nor the ground station can read what they carry.
05 · A fleet’s exit

A fleet with no fixed address leaves through one exit.

Field teams and vehicles on cellular have no address of their own and change networks constantly, yet their traffic to the internet has to leave from one known place.

The fleet
Phones, laptops and vehicle nodes behind carrier NAT.
The exit
A hosted exit on a relay host, chosen by measured round trip; or a private exit on a node at headquarters, itself behind NAT.
Carried by
The bond, straight to the hosted exit’s public address; to a private exit, the same relay modes as any member.
Configured
Hosted: a [[peer]] carrying 0.0.0.0/0 and [leak_guard]; the Android app with one switch. Private: [exit] on the headquarters node, naming the members it forwards for.
What you get
The internet sees one address, the exit’s. DNS stays in the tunnel, and with the leak guard the uplinks carry nothing but the daemon’s own traffic. The exit decrypts what it carries to the internet, as any internet gateway does.
Get early access

Bring us the network you cannot control.

Apply as a pilot partner if you have a deployment ready to test, or start evaluating Nexus Atlas Traversal as a future customer. Tell us enough to understand the endpoints, carriers, regions, and operational constraints involved.

01

Pilot partner

Run an early deployment with direct engineering contact and help shape priorities through real-world feedback.

02

Customer evaluation

Research architecture, security, deployment options, and commercial fit before committing to a pilot.

Already enrolled? Open the console
Early-access applicationUsually answered by the product team

Your application is sent to the Nexus Atlas product team. You can also email office@nexusatlas.io.