02 · Two fleets, one seamTwo 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.