SDKs and platforms

How do NVIDIA Jetson boards communicate over Bluetooth and Wi-Fi without internet?

Run Offline Protocol on the Jetson. It finds nearby devices and exchanges end-to-end encrypted messages with them over the local network (Ethernet or Wi-Fi) and Bluetooth LE, relaying through other devices, with no internet or server. Install the aarch64 wheel on JetPack 6 or 7, run the arm64 service image, or deploy it with WendyOS.

TL;DR

A Jetson Orin on JetPack 6 or 7 installs the Offline Protocol aarch64 wheel and runs a full peer on its CPU, beside its GPU workloads. JetPack 5 runs the arm64 service image instead. Under WendyOS, a Jetson Orin Nano runs an Offline Protocol app with no internet.

Learning objectives

After reading this article you will be able to:

  • Check which JetPack releases install the Offline Protocol aarch64 wheel directly
  • Choose between the Python package, the service container and WendyOS on a Jetson
  • Place a Jetson in a fleet beside other boards and phones, with no internet

Jetson support in Offline Protocol

An NVIDIA Jetson Orin module is a 64-bit Arm computer that runs Jetson Linux, NVIDIA’s Ubuntu-based operating system. To Offline Protocol it is an ordinary Linux aarch64 host, so it takes the same packages as a Raspberry Pi or an Arm server:

PackageWhat the Jetson gets
Python, offline-protocol-sdkThe manylinux_2_34_aarch64 wheel, with the native library inside
The service containerghcr.io/offline-protocol/offline-protocol-service, published for linux/arm64
Java and CThe linux-aarch64 native library from the GitHub release
RustThe crates, built for aarch64-unknown-linux-gnu

Python is the place to start. It ships the transport bridges a host needs (local network peer streams, Bluetooth LE, an internet relay client and a gateway client), so one install gives a Jetson a working peer:

pip install 'offline-protocol-sdk[lan]'

Bluetooth LE, Wi-Fi and Ethernet on a Jetson

A Jetson running Offline Protocol uses every link it has at the same time, and needs no internet connection or server for any of them:

  • Wi-Fi and Ethernet. Devices on the same local network find each other over DNS-SD and connect with encrypted peer streams, with no addresses configured.
  • Bluetooth LE. On a Jetson with a Bluetooth adapter, the Offline Protocol service talks to nearby boards and phones through BlueZ, with no Wi-Fi network and no pairing.
  • Other devices in between. When two devices cannot reach each other directly, a device that can reach both relays the traffic, end-to-end encrypted, so it cannot read what it carries.

Messages for a device that is out of range are held on disk and delivered when it comes back. Every session and group is encrypted with MLS (RFC 9420), and each Jetson has its own identity.

JetPack versions and glibc 2.34

The Linux wheels need glibc 2.34 or newer. Which JetPack a Jetson runs decides whether pip finds a wheel:

JetPackRoot file systemglibcThe wheel
JetPack 7Ubuntu 24.042.39Installs
JetPack 6.2Ubuntu 22.04 (Jetson Linux 36.4.3)2.35Installs
JetPack 5.1.2Ubuntu 20.04 (Jetson Linux 35)2.31Use the container

NVIDIA lists JetPack 6.2 for the Jetson Orin Nano and Orin NX modules and any Jetson Orin developer kit, and JetPack 7 for Jetson Orin and Jetson Thor. On a JetPack 5 host, the service image runs anyway, because a container carries its own userland: the image is built on Debian’s python:3.12-slim, which has a new enough glibc. Alpine-based images do not work, because the wheels are built for glibc, not musl.

Offline Protocol beside GPU workloads

The engine does its discovery, routing and MLS encryption on the CPU, and it never touches the GPU. A Jetson can run a detector or a planner on CUDA and use Offline Protocol for everything that crosses to another machine: publishing a detection, answering a request from a robot nearby, or handing a task to a phone. With the service and its HTTP front, a model server on the Jetson becomes a service other devices call with a plain HTTP request, end-to-end encrypted, with no networking code in the model server. How to call an HTTP service on another device without internet covers the pattern.

Jetson on WendyOS

WendyOS, Wendy Labs’ operating system for robots and edge AI devices, runs on Jetson Orin and deploys each app as a container that lists what it needs in wendy.json. An Offline Protocol app asks for host networking, so multicast DNS discovery reaches the local network, and a persistent volume, so the board keeps its identity and its held messages across deploys. WendyOS updates the operating system over the air on Jetson Orin, writing each update to a second partition and rolling back by itself if it fails.

Wendy Labs ran one Offline Protocol app on a Jetson Orin Nano, a Raspberry Pi 5 and a Qualcomm Dragonwing IQ9, all on WendyOS and a router with no internet. The Jetson found the other boards with no address configured, opened MLS sessions with them, and received every message they held for it after its network cable was pulled and plugged back in. Offline Protocol on WendyOS shows each step, and How do I deploy a mesh app to a fleet of boards? covers the deployment.

Jetson in a fleet with other devices

A Jetson rarely works alone. Because every platform runs the same protocol, it joins one encrypted mesh with:

  • Other boards. Raspberry Pis, Dragonwing boards and other Linux hosts on the same network find each other over DNS-SD, and a board in the middle relays for two that cannot reach each other.
  • Phones. An iPhone or Android phone running an app on the SDK reaches the Jetson over the local network or, with a Bluetooth adapter on the Jetson, over Bluetooth LE through BlueZ.
  • The internet, when there is one. One gateway on the site holds the uplink, and the Jetsons and other boards reach each other locally whether or not it is up.

Each Jetson keeps its keys in the SDK’s file stores, sealed under a store key, because a headless board usually has no keyring. Generate a store key per board, keep it in your secret store, and mount a persistent volume for the state.

Frequently asked questions

Which Jetson modules can run Offline Protocol?

Jetson Orin modules, such as the Orin Nano, Orin NX and AGX Orin, on a JetPack release with glibc 2.34 or newer. JetPack 6 is built on Ubuntu 22.04 and JetPack 7 on Ubuntu 24.04, and both meet that floor. JetPack 7 also covers Jetson Thor.

Does Offline Protocol use the Jetson's GPU?

No. The engine does its networking and encryption on the CPU, so the GPU stays free for your models. A typical Jetson app runs inference on the GPU and uses Offline Protocol to share the results with other devices.

Can I run Offline Protocol on a Jetson with JetPack 5?

Yes, in a container. JetPack 5 is built on Ubuntu 20.04, whose glibc 2.31 is older than the wheel needs, so pip finds no wheel on the host. The published service image for linux/arm64 brings its own Debian userland and runs there.

Can a Jetson talk to phones and Raspberry Pis with Offline Protocol?

Yes. Every platform runs the same protocol, so a Jetson, a Raspberry Pi and an iPhone or Android phone running an app on the SDK form one encrypted mesh. With a Bluetooth adapter, the Jetson also runs both Bluetooth LE roles through BlueZ.

How do I deploy an Offline Protocol app to several Jetsons?

Build one arm64 container image and deploy it to each board with a persistent volume for its identity and held messages. On WendyOS, wendy run does this for each board, and a build host can build once and deploy to several devices.

Sources

Build it with Offline Protocol

The Python page covers installing the wheel, the store key for a headless host, and starting a peer on a Linux host over the local network.

Read Python and Linux gateways