Skip to content

Transports

MeshSat supports 10 transport types across four categories. Each transport handles the protocol-specific details of sending and receiving messages, while the policy engine handles routing between them.

Mesh Networks

TransportInterfaceStatusDescription
MeshtasticSerial / USBStableLoRa mesh radios (T-Echo, Heltec, RAK, etc.)
ZigBeeSerial / USBBetaIEEE 802.15.4 mesh via ZigBee coordinator dongles

Satellite

TransportInterfaceStatusDescription
Iridium SBDSerialStableShort Burst Data via RockBLOCK 9603N
Iridium IMTSerialBetaInternet Modem Transceiver via RockBLOCK 9704

Cellular

TransportInterfaceStatusDescription
CellularSerial / USBStableSMS and data via USB cellular modems (Huawei E220, etc.)

IP Networks

TransportInterfaceStatusDescription
MQTTTCP/TLSStablePublish/subscribe messaging over MQTT brokers
WebhooksHTTP/HTTPSStableIncoming and outgoing HTTP webhooks
APRSTCP (APRS-IS)BetaAmateur Packet Reporting System for position and telemetry
TAKTCP/TLSBetaTeam Awareness Kit (ATAK/WinTAK) CoT integration

Transport Lifecycle

Every transport follows the same lifecycle:

  1. Init — Transport is created with its configuration
  2. Connect — Underlying connection is established (serial port opened, TCP connected, etc.)
  3. Run — Transport listens for incoming messages and accepts outgoing sends
  4. Reconnect — On connection loss, transport automatically retries with exponential backoff
  5. Shutdown — Graceful disconnect on process exit

Common Features

All transports share these capabilities:

  • Auto-detection — Serial transports can auto-detect device ports on USB hotplug
  • Health checks — Each transport reports its connection status via the API
  • Metrics — Per-transport message counts, latency, and error rates
  • Dead letter queue — Failed sends are queued for retry with configurable TTL
  • Message transforms — Payloads can be transformed before sending (compression, encoding, format conversion)

Next Steps

Select a transport above for detailed configuration and usage instructions, or see the Architecture section to understand how transports interact with the policy engine.

Made by MeshSat