mosh:transports
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| mosh:transports [2025/06/25 15:59] – mosh | mosh:transports [2026/06/10 13:55] (current) – mosh | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <WRAP important> | ||
| + | This page is retained for historical reference and may not reflect the current MOSH/ | ||
| + | See [[guide: | ||
| + | </ | ||
| ====== MOSH Transports ====== | ====== MOSH Transports ====== | ||
| Line 28: | Line 32: | ||
| * Espressif ESP-NOW(V1) | * Espressif ESP-NOW(V1) | ||
| * Espressif ESP-NOW(V2) | * Espressif ESP-NOW(V2) | ||
| - | * WiFi | + | * Wi-Fi |
| * Serial | * Serial | ||
| + | * Bluetooth (future) | ||
| + | * nRF24L01 (future) | ||
| + | * nRF52840 (future) | ||
| + | * LoRa (future) | ||
| + | |||
| + | MOSH is designed to abstract the transport layer so that core functionality (messaging, routing, automation) remains consistent regardless of whether messages are transmitted via ESP-NOW, Wi-Fi, Serial, or future transports. | ||
| ==== ESP-Now (v1 and v2) ==== | ==== ESP-Now (v1 and v2) ==== | ||
| Line 37: | Line 47: | ||
| ESP-NOWv1 supports payloads up to 250 bytes. In version 2 (unofficial community extension or modified firmware), payloads up to 1470 bytes may be supported, typically by layering on top of Wi-Fi frames. | ESP-NOWv1 supports payloads up to 250 bytes. In version 2 (unofficial community extension or modified firmware), payloads up to 1470 bytes may be supported, typically by layering on top of Wi-Fi frames. | ||
| - | ==== WiFi ==== | + | ==== Wi-Fi ==== |
| - | WiFi is a wireless protocol defined by the IEEE in the 802.11 protocol standard. MOSH can use Wi-Fi as a transport, often over TCP or UDP sockets. This provides features like encryption (via TLS), reliable delivery (via TCP), and long-range routing. However, Wi-Fi is not required for a functional MOSH networks. | + | Wi-Fi is a wireless protocol defined by the IEEE in the 802.11 protocol standard. MOSH can use Wi-Fi as a transport, often over TCP or UDP sockets. This provides features like encryption (via TLS), reliable delivery (via TCP), and long-range routing. However, Wi-Fi is not required for a functional MOSH networks. |
| ==== TTL Serial (UART) ==== | ==== TTL Serial (UART) ==== | ||
| TTL Serial (UART) is commonly used by MCUs for programming or debugging, but it can also be used for MOSH communication between nodes. This is especially useful for bridging different transport -- for example, a MOSH Controller can connect a UART node to an ESP-NOW or Wi-Fi network, acting as a gateway. | TTL Serial (UART) is commonly used by MCUs for programming or debugging, but it can also be used for MOSH communication between nodes. This is especially useful for bridging different transport -- for example, a MOSH Controller can connect a UART node to an ESP-NOW or Wi-Fi network, acting as a gateway. | ||
| + | |||
| + | ===== Transport Bridging ===== | ||
| + | |||
| + | MOSH provides a built-in method of bridging transports together. These bridges, called MOSH Controllers, | ||
/var/www/wiki.moshnetworks.com/data/attic/mosh/transports.1750867169.txt.gz · Last modified: by mosh
