[ INTEGRATION SURFACE · BETA ] ━━ API, SDKs, and event payloads may change between releases. Read the versioning policy ▸
▸ ROOT / DEVELOPERS/ NETWORK SETUP

Network Setup

How to connect a Cheetah inspection cell to your facility network and give it a fixed IP address.

▸ BETA

A Cheetah inspection cell joins your facility network through a single Ethernet connection. Once it has an address, anyone on that network can integrate with the open REST API.

This page covers what to plan for before the cell arrives, how to give it a fixed IP address, and how to confirm it is reachable.

Contents#

Network connection#

Connect your facility network to the WAN port on the user expansion panel. The LAN ports are reserved for the cell's internal components.

Before installation#

Gather the following with your IT or network team:

  1. The IP address the cell should use.
  2. Subnet conflicts. The cell uses 192.168.57.0/24 and 192.168.58.0/24 internally to reach its own devices. If your facility network uses either range, tell Cheetah before installation so the cell's device network can be moved.

Assign a fixed IP address#

The cell requests an address with DHCP. Your users and integrations should reach it at a predictable address, so reserve one for it in your DHCP server. No change is needed on the cell.

  1. Connect the WAN port to your network and power on the cell.
  2. In your DHCP server or router, find the new lease. The cell identifies itself by its hostname, your company name followed by -kiosk (for example acme-kiosk).
  3. Note the lease's MAC address.
  4. Create a reservation that binds that MAC address to the IP address you chose.
  5. Unplug the WAN cable for a few seconds and plug it back in, or restart the cell. It now comes up at the reserved address every time.

Connect and verify#

From a computer on the same network, replace <cell-ip> with the cell's address:

  1. Ping it: ping <cell-ip>
  2. Check the API: curl http://<cell-ip>:8000/health should return a 200 with per-component status. The quickstart continues from here.

If both succeed, the cell is successfully on your network.

Open API access#

The open REST API is served on TCP port 8000 at the cell's address, e.g. http://<cell-ip>:8000. Allow TCP 8000 to the cell from any system that integrates with it.

Troubleshooting#

Symptom Likely cause Solution
No DHCP lease appears for the cell Cable not in the WAN port, or no DHCP server on that segment Connect to WAN; confirm DHCP is served on that segment
API calls fail Port 8000 blocked Allow TCP 8000 inbound to the cell
Cell reaches your network but not its own sensors or robot Your network overlaps 192.168.57.0/24 or 192.168.58.0/24 Contact support to move the device network
▸ LAST VERIFIED Fri Oct 30 2026 00:00:00 GMT+0000 (Coordinated Universal Time) ▸▸ /content/developers/network-setup.md
▸ DOCS UNDER CONSTRUCTION LAST UPDATED 2026-11-18 ▸ CHANGELOG