Changing attachment
Tower and carrier transitions can replace the outer address without changing the vehicle’s Atlas identity.
A fleet vehicle may change cell towers, private addresses, carriers, and access technology throughout one route. Atlas anchors communication in cryptographic identity and treats every reachable route as measured inventory.
Carrier NAT permits the vehicle to initiate traffic but usually prevents another endpoint from dialing back. Address changes make static tunnels brittle even when inbound reachability exists briefly.
Tower and carrier transitions can replace the outer address without changing the vehicle’s Atlas identity.
CGNAT means many subscribers share public addresses and inbound rules are outside the fleet operator’s control.
Direct and relayed routes over one modem improve reachability but still share the same underlying radio failure.
Atlas applications continue to use the same interface and peer identities as the vehicle moves.
Relay sessions establish through outbound cellular connectivity.
A direct carrier path appears where current NAT policy permits it.
Authenticated packets adopt the vehicle’s valid new outer address.
Measurements move traffic away from a weak or disappearing path.
Reappearing paths rejoin the scheduler without rebuilding the tunnel.
Traversal supports the reachability layer; the wider Atlas configuration defines which peers, routes, and traffic policies each fleet needs.
Every vehicle reaches one or more command sites through public, private, or hybrid relay estates.
Peers can rendezvous through relays and add direct connectivity where carrier policy allows it.
Devices behind the onboard Atlas node use the tunnel without each device needing traversal awareness.
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.
Run an early deployment with direct engineering contact and help shape priorities through real-world feedback.
Research architecture, security, deployment options, and commercial fit before committing to a pilot.