UAS4G5G LTE · NETWORK & VPN

ZeroTier, step by step.

Create a private network, join both devices, authorise members and use the assigned IPs for UAS.

THE CONNECTED FLIGHT PLATFORMv23Raspberry Pi
Radxa ROCK 4D
Radxa ZERO 3W / 3E
01

Before you connect

Join the board and ground station to the same authorised virtual network.

This guide covers current New Central and Legacy Central, with screenshots, UAS controls, address selection and troubleshooting.

The workflow applies to Raspberry Pi, Radxa ROCK 4D and ZERO 3W/3E. Both devices need internet, and the receiving computer/phone needs the ZeroTier client. Logging in to Central in a browser does not itself join that computer to the network.

UAS licensing is local. ZeroTier is an optional networking service with separate account/network policies. Use its real assigned IPs; screenshot IDs and addresses are examples only.

Read the numbered steps below. You do not need Tailscale and ZeroTier together for a basic setup.

Reviewed: 3 November 2026. Service interfaces and account terms can change. Technical sources and screenshot credits are linked beside each relevant step.

02

1. Create or select your network

Official ZeroTier example; the red circle identifies Network ID. Do not use its sample values. Source ↗.

New Central — central.zerotier.com

Sign in and complete the organisation/plan setup if you are new. Open your network under Networks, then copy the 16-character hexadecimal Network ID shown at the top. The screenshot highlights its location.

Legacy Central — my.zerotier.com

Open an existing network, or choose Create A Network, then copy its Network ID. Keep a private, authorised-members network for your own devices.

Use a managed IPv4 range that does not overlap the board's hotspot (192.168.77.0/24), your normal LAN or another connected VPN. Ordinary board-to-PC access does not need a LAN bridge or an internet default route.

Official quickstart—both Central versions ↗ · Network settings ↗.

Image: official ZeroTier documentation. Do not join the example network printed in the picture; copy your own ID.

03

2. Join from UAS and the ground station

Current UAS interface; ① is the ZeroTier join control and ⑤ the shared VPN Console. Tailscale is a separate option.

On the board

  1. Open UAS locally and go to UAS Settings / UAS Stettings.
  2. In screenshot ①, paste your ZeroTier Network ID, then press Set.
  3. Read ⑤ VPN Console. Joining requests membership; it does not by itself approve the board.

On the ground station

  1. Install the official client from ZeroTier Downloads ↗.
  2. On Windows/macOS, open its tray/menu-bar icon → Join New Network, paste the same Network ID, then Join. On mobile, add the network in the app and enable its VPN connection/OS permission.
  3. On Linux with the client installed, use sudo zerotier-cli join YOUR_NETWORK_ID if you prefer the terminal.

Both devices must appear in the same Central network. The next step is authorisation.

Raspberry and Radxa have the same ZeroTier controls shown here. The Tailscale controls below are unrelated to this join operation.

Official join procedure ↗.

04

3. Authorise in New Central

Official ZeroTier annotated screenshot. Match the device before authorising it. Source ↗.
  1. Open your network's Member Devices tab.
  2. Identify the board and ground station by their Device / Node ID. Authorise only the devices you recognise.
  3. For each Not Authorized member, open Actions ⋯ → Authorize.
  4. Give each device a clear name and note its assigned ZT IP.

Refresh Central if a newly joined member has not appeared yet. Use the per-device menu shown in the screenshot, so you can check each member individually.

You need two authorised devices, not just a working browser login to Central. An authorised member still needs a usable IP and permitted traffic rules.

Official member management ↗. Screenshot: ZeroTier documentation. The shown names, IDs and addresses are the provider's example.

05

4. Authorise in Legacy Central

Official ZeroTier annotated screenshot; this is the Legacy interface. Source ↗.

If you use my.zerotier.com, open the network and scroll to Members.

  1. Match each Address to the correct device's 10-character Node ID.
  2. Tick Auth? for the board and the ground station.
  3. Add recognisable names and read their Managed IPs.

The screenshot's “Address” is a device identifier—not the IP you type into UAS or a video endpoint. The Managed IPs column holds the virtual network addresses.

If a member is missing, check your filters and that the device joined this exact Network ID. Keep the network private; making it public is not a fix for a missed authorisation.

Legacy authorisation instructions ↗. Screenshot: official ZeroTier documentation; its sample values are not your configuration.

06

5. Network ID, Node ID and assigned IP

  • Network ID: 16 hexadecimal characters. Enter this in the UAS ZeroTier field to join a network.
  • Device / Node ID: 10 hexadecimal characters. Identify the board/PC in the member list.
  • ZT IP / Managed IP: the actual virtual IP assigned to that device. Use this for dashboard access and stream destinations.

Example only

Board: 10.147.17.10 · Ground PC: 10.147.17.20 From the connected ground PC, open: http://10.147.17.10:3000/uaslte/

Use your own board's address, without a subnet suffix such as /24 in the browser URL. UAS Dashboard → Link & Network shows its ZeroTier information; Central shows the member assignments.

If the board is authorised but has no managed IP, review IPv4 assignment and matching managed routes in Central. Do not randomly overwrite the board's physical LAN/Wi-Fi address.

The program's normal dashboard login/licence still applies.

Identifiers and membership ↗ · IP assignment and managed routes ↗.

08

7. Read the status correctly

In UAS: inspect Dashboard → Link & Network and the result in the VPN Console after Set. Confirm the expected network and assigned IP.

Optional diagnostics on a computer with ZeroTier installed

zerotier-cli info zerotier-cli listnetworks zerotier-cli peers Use an administrator terminal / sudo where required.

  • ONLINE in node status means the client can contact ZeroTier infrastructure; it does not prove this network is authorised.
  • OK in the network list is the membership state you want; also check the assigned IP.
  • ACCESS_DENIED: authorise that member in the correct network.
  • REQUESTING_CONFIGURATION: allow negotiation to complete; if it persists, check the ID and connectivity to the controller.
  • NOT_FOUND: check the Network ID.
  • DIRECT / RELAY in peers describes the path to a particular peer. Inspect the other device, not merely a root-server entry.

Official CLI/status reference ↗ · Relayed connections ↗.

A relayed path can be usable but may add delay. It is not a camera-encoding fault by itself.

09

8. Leave, rejoin and keep the identity

Set requests joining the Network ID you entered. Confirm the actual result before sending streams.

Leave ZT network leaves the joined network. Its remote route is no longer available; reconnect locally or through another working path before changing it back.

Erase secret key is not a disconnect button. It removes the stored ZeroTier identity key. A new identity can require fresh authorisation and may receive a different assigned IP. Use it only when deliberately repairing/replacing the device identity.

For normal use, keep the stored identity. After a routine reboot, check the existing network/IP rather than recreating the network or erasing the identity.

After replacing/reimaging a board, verify its actual Node ID and authorise the intended member; do not assume an old Central entry belongs to the new instance. Update any endpoints whose assigned IP changed.

Never copy one device's ZeroTier identity to several running boards. Each active device needs its own identity.

ZeroTier identity and connection troubleshooting ↗.

10

9. Troubleshoot and test remotely

  1. Internet: both devices online; local UAS working first.
  2. Membership: same Network ID; both authorised; usable ZT IPs.
  3. Address: browser uses the board's ZT IP and :3000/uaslte/; external streams use the receiver's ZT IP.
  4. Routes: no overlapping LAN/hotspot/VPN subnet; managed addressing accepted by the client.
  5. Policy/firewall: permit the intended service or receiver, not indiscriminate public access. Ping can be blocked independently of the application.
  6. Application: camera detected/started, correct codec, external receiver listening on the exact configured UDP port.
  7. Path/quality: inspect peer connectivity, mobile upload and packet loss. Test another ground network if the path is relayed or unstable.

A stricter carrier/router can prevent a direct path. Do not blindly forward the UAS web port to the public internet or change MTU as a universal fix.

Ping troubleshooting ↗ · Router/NAT guidance ↗.

Final test: use two different internet connections; confirm dashboard, live video and MAVLink independently, then verify a normal reconnect/reboot on the ground. Alternative: Tailscale guide.

11

Continue with the program

Program screenshotFull resolution ↗