Meshtastic

Meshtastic is an open-source system that turns small LoRa radios into an off-grid, decentralized network for short text messages, positions, and telemetry. LoRa (Long Range) is a low-power radio modulation technique designed to move small amounts of data over comparatively long distances. Meshtastic can work without mobile coverage, Wi-Fi, or an internet connection, although internet bridging is available as an option. Meshtastic Introduction Meshtastic Technical Overview

The simplest analogy is a walkie-talkie for text messages. Instead of speaking into a microphone, you type on a phone or computer. Instead of the message travelling through a mobile operator, a nearby Meshtastic radio broadcasts it over LoRa. Other compatible radios may relay the packet until it reaches its recipient. Meshtastic Technical Overview

That analogy is useful, but Meshtastic is not voice radio. Its low data rate suits text, GPS positions, device status, and sensor readings—not normal voice calls, video, websites, or large files. A packet can carry an encrypted application payload of up to 239 bytes, with roughly 200 bytes available for application data after its internal fields. Meshtastic Packet Overview

What problem does Meshtastic solve?

Most everyday communication depends on external infrastructure: a mobile network, internet provider, platform, or remote server. If that infrastructure is unavailable, the application stops working.

Meshtastic provides a small, locally operated alternative for low-volume data. The radio network itself does not require a base station, subscription, SIM card, central router, or cloud service. Compatible nodes communicate directly and may rebroadcast packets for one another. The project is community-driven and open source. Meshtastic Introduction

It suits brief updates such as “We reached the mountain hut,” “Meet at checkpoint three,” or “My position is here.” Meshtastic is therefore an additional low-bandwidth communication layer, not a smaller replacement for the internet.

The walkie-talkie-for-text analogy

Imagine two ordinary walkie-talkies. If the radios are tuned to compatible settings and are within range, one person can speak and the other can hear. A hill, a concrete building, or too much distance may break the link.

Now make three changes:

Replace speech with small digital packets.
Connect the radio to an application that displays text, contacts, positions, and device information.
Allow other radios to repeat eligible packets.

That is the basic Meshtastic idea.

The third change creates the mesh. If Ana cannot reach Boris directly, but both can reach a well-placed node on a hill, that node may relay the message:

Ana → hilltop node → Boris

The relay does not need Ana’s private key. Routing metadata remains unencrypted, allowing nodes to forward application payloads they cannot read. Meshtastic Encryption Meshtastic Technical Overview

What you need to get started

For normal phone-based use, you need:

A Meshtastic-compatible LoRa device made for the correct regional frequency band
Meshtastic firmware on that device
A suitable antenna
A phone, tablet, or computer running a Meshtastic client
Bluetooth, USB/serial, Wi-Fi, or Ethernet connectivity between the client and radio, depending on the hardware
Battery or USB power

The official hardware list includes development boards, portable units, trackers, and standalone devices. Features vary, so check the current list before buying. Meshtastic Supported Hardware

GPS or another Global Navigation Satellite System receiver is optional. Some devices include one, some accept an optional module, and some have none. A GPS-equipped node can obtain and share its position; a phone may also provide position data, depending on the client and configuration. Environmental or device sensors are also optional, and Meshtastic’s telemetry module can periodically transmit supported readings. Meshtastic Supported Hardware Meshtastic Telemetry Module

One node is enough to listen for and join an existing compatible mesh. To test an independent link where no other nodes exist, you need at least two.

How a Meshtastic message travels

This is the core process.

1. You write a message in the app

You open a Meshtastic client on a phone or computer, choose a channel or recipient, and enter a short message.

The app supplies the screen and keyboard; the node handles radio communication.

2. The app sends the message to your node

The client passes the message to the Meshtastic radio over Bluetooth, Wi-Fi/Ethernet, or a serial connection such as USB. A phone is therefore not transmitting LoRa itself; it is instructing the connected node. Meshtastic Technical Overview

3. The node prepares and encrypts the packet

For channel traffic, the application payload is encrypted with that channel’s pre-shared key, or PSK—a secret shared by the members of the channel. Current Meshtastic documentation describes AES-256 in CTR mode for payload encryption, with a different key available for each channel. The routing header remains visible so other nodes can forward the packet. Meshtastic Encryption

The packet also contains routing information including sender, destination, packet ID, channel hash, and hop-limit data. Meshtastic Technical Overview

4. Your node broadcasts the packet over LoRa

LoRa is a broadcast radio medium: nearby compatible nodes using the same frequency, bandwidth, and spreading factor can receive the transmission. Meshtastic groups these radio parameters into modem presets to make compatible configuration easier. Meshtastic Technical Overview Meshtastic LoRa Configuration

If the sending node does not receive confirmation from another device after a timeout, the official overview says it may retransmit the message up to three times. Retries improve the chance of reception, but they cannot guarantee delivery. Meshtastic Technical Overview

5. Nearby nodes decide whether to rebroadcast it

A receiving node checks the packet ID to see whether it has already heard that packet. A duplicate is ignored. A new packet may be rebroadcast if the node’s role and rebroadcast configuration permit it. Meshtastic Technical Overview Meshtastic Device Configuration

This duplicate check is essential. Without it, nodes could repeat the same message indefinitely and rapidly fill the channel with copies.

6. Every relay reduces the hop limit

The hop limit is the maximum number of times a packet may be rebroadcast. Each forwarding node decrements it by one. A node receiving a packet with a hop limit of zero does not forward it again. Meshtastic allows a maximum configured hop limit of seven and uses three by default; the project documentation explicitly says three is sufficient for most uses. Meshtastic Technical Overview Meshtastic LoRa Configuration

For example, a packet sent with hop limit 3 may be forwarded with values 2, 1, and finally 0. The next receiver may use it but will not relay it again.

7. The destination decrypts and displays the message

A receiving node with the appropriate channel key can decrypt and interpret the payload, then pass the decoded message to its connected client app. A compatible node without that key may still relay the packet, but it cannot display the protected content. Meshtastic Technical Overview Meshtastic Encryption

8. If the app is disconnected, the node keeps a small buffer

Meshtastic radios store a small number of packets—around 30—while no client app is connected. When the buffer is full, the oldest stored packets are replaced by newly arriving text messages. This is a convenience buffer, not a permanent mailbox or full message history. Meshtastic Technical Overview

This means you can leave a node operating and later reconnect your phone to receive a limited set of recent packets. It does not mean every message sent during a long absence will wait indefinitely.

What LoRa provides—and what it gives up

LoRa uses Chirp Spread Spectrum (CSS) modulation. In simple terms, it represents data using signals that sweep across a frequency range. Meshtastic’s documentation explains that higher spreading factors can improve range and reliability, but increase airtime and reduce data rate. Meshtastic Technical Overview

The practical trade-off is:

Long range: especially with clear line of sight and useful antenna height
Low power: suitable for portable, battery, and carefully designed solar nodes
Low data rate: suitable for brief packets, not high-bandwidth media

Meshtastic cites a 331 km range record, but this was a record-setting link, not a promise of normal coverage. Records depend on exceptional terrain, elevation, antennas, radio conditions, and configuration. Treat them as demonstrations of what may be possible under extreme ideal conditions—not as a buying guide. Meshtastic Introduction

In normal use, a node inside a building at street level may struggle to cross part of a city, while a modest node on a mountain with clear line of sight may reach far beyond it. The official radio documentation confirms the technical speed-versus-range trade-off between modem presets; actual coverage must still be measured locally. Meshtastic LoRa Configuration

This is why more transmit power is not the universal answer. A better antenna position, more height, fewer obstructions, correct orientation, and a useful relay location may matter more than increasing output power. Any power and antenna combination must also remain within local regulatory limits.

Read Antennas, height, and real-world range before planning a permanent node.

What “mesh” really means

A Meshtastic radio mesh is a set of nodes using compatible LoRa settings: the same spreading factor, center frequency, and bandwidth. A node cannot simultaneously participate in another radio mesh using different values. Meshtastic presets make matching these parameters easier. Meshtastic Technical Overview

The mesh can extend coverage because nodes relay eligible packets. It does not create unlimited range.

Every useful path still depends on working radio links, compatible settings, sufficient hop limit, powered and correctly configured nodes, available airtime, and packets avoiding collisions and interference.

Meshtastic uses controlled rebroadcasting, not guaranteed paths and reserved capacity. Delivery can fail. Acknowledgements and retries help, but cannot guarantee service on a shared radio channel. Meshtastic Technical Overview

More nodes can improve reach only when they add useful radio paths. Dozens of nearby nodes repeating similar traffic may instead increase congestion. A small number of stable, elevated nodes can be more useful than many nodes clustered indoors.

For the differences between ordinary clients and infrastructure roles, read Node roles explained.

Channels, encryption, and privacy

Meshtastic separates the radio mesh from logical channels.

Nodes first need compatible LoRa radio settings to hear one another. On top of that shared radio mesh, each logical channel has a name and encryption key. A node can have up to eight channels. Only nodes with the matching channel name and key can normally decrypt and display that channel’s messages, but other nodes in the same radio mesh may still receive and relay those packets. Meshtastic Technical Overview

Meshtastic supports channel pre-shared keys based on AES-128 or AES-256 sequences; its encryption overview describes AES-256-CTR for LoRa payloads. Encryption can also be disabled. Meshtastic Radio Settings Meshtastic Encryption

This should not be summarized as “anonymous” or “fully private”:

Routing metadata is not encrypted.
Radio transmissions can be detected by nearby receivers.
Everyone with a shared channel key can read that channel.
The documented channel PSK design does not authenticate messages, so someone possessing the PSK may impersonate another user on that channel.
A compromised or casually shared key compromises the channel’s confidentiality.

Meshtastic Encryption Limitations

Encryption protects message content from casual reading when configured correctly. It does not hide the fact that radios are transmitting, prove every sender’s identity, or remove the need to protect keys.

Read Channels, encryption, and privacy for the deeper explanation.

Frequency bands, licences, and Serbia

Meshtastic commonly operates in licence-exempt ISM/SRD bands—spectrum made available for industrial, scientific, medical, or short-range radio devices under specified conditions. “Licence-exempt” does not mean “without rules.” Frequency, effective radiated power, duty cycle, bandwidth, and equipment requirements depend on the country and band.

Meshtastic currently exposes 26 region-code values in its LoRa configuration table when UNSET is included: 25 transmitting region presets plus the non-transmitting UNSET state. A new node will not transmit until a region is selected. Meshtastic LoRa Configuration

The country reference lists Serbia under both EU_868 and EU_433. Meshtastic Region by Country

For the commonly used EU_868 setting, Meshtastic configures:

Frequency range: 869.4–869.65 MHz
Firmware duty-cycle limit: 10%
Power limit: 27 dBm

Meshtastic LoRa Configuration

RATEL’s current Rulebook lists the 869.4–869.65 MHz sub-band for non-specific short-range devices at up to 500 mW e.r.p., with less than 10% duty cycle or LBT+AFA. Here, e.r.p. means effective radiated power relative to a half-wave dipole; LBT means Listen Before Talk, and AFA means Adaptive Frequency Agility. The rulebook was published in Serbia’s Official Gazette No. 88/2024 and entered into force on 15 November 2024. RATEL Rulebook, Annex 1, Table 1.1

Because 500 mW is approximately 27 dBm, the values align numerically, but users must follow the RATEL rulebook—not merely assume that every setting exposed by firmware is lawful in every installation. Antenna gain and the difference between transmitter output and effective radiated power also matter.

For ordinary compliant SRD operation, users generally rely on the general-authorization regime rather than obtaining an individual amateur-radio licence. Amateur operators can experiment with Meshtastic under applicable amateur rules, but Meshtastic is not amateur radio by default. Encryption restrictions may apply when operating in amateur allocations, which is one reason Meshtastic permits encryption to be disabled. RATEL Rulebook Meshtastic Radio Settings

Read Legal frequency rules for Serbia and Europe before changing transmit power, using a high-gain antenna, or installing permanent infrastructure.

Common Meshtastic uses

Meshtastic is useful when people need short, occasional messages or small data packets and conventional connectivity is weak or unwanted.

Common uses include:

Hiking and outdoor group coordination
Camping, overlanding, and remote travel
Community-operated local networks
Position sharing for people, vehicles, or equipment
Festivals and events
Telemetry from batteries and environmental sensors
Radio-propagation and electronics experiments
A secondary communication path during local internet or mobile outages
Emergency-preparedness exercises

Official modules include telemetry, range testing, serial data, remote hardware control, and optional store-and-forward functions. Device roles include tracker and sensor modes alongside the default client role. Meshtastic Module Configuration Meshtastic Device Configuration

For most beginners, the default CLIENT role is the correct starting point. A client can send, receive, and rebroadcast eligible traffic. Dedicated roles should be chosen for a defined purpose, not merely because their names sound more powerful. Meshtastic Device Configuration

What Meshtastic is not

It is not LoRaWAN

LoRa is the radio modulation used by both systems. LoRaWAN is a separate standardized network protocol and architecture in which end devices normally communicate through gateways and network servers. Meshtastic uses its own peer-to-peer mesh protocol and does not require or use a LoRaWAN gateway for normal mesh communication. LoRa Alliance: What is LoRaWAN? Meshtastic Technical Overview

It is not mobile internet

Meshtastic can move small messages and data packets. It does not provide ordinary web browsing, streaming, social-media access, or a general IP internet connection. Its maximum on-air packet and application-payload sizes are measured in hundreds of bytes, not megabytes. Meshtastic Technical Overview

It is not normal voice radio

Sub-GHz Meshtastic meshes are intended for low-rate data rather than continuous speech. Meshtastic documents an experimental audio module for certain 2.4 GHz hardware, but explicitly says sub-GHz bands are not wide enough for continuous audio packets on the mesh. That experiment does not turn normal Meshtastic nodes into walkie-talkies. Meshtastic Audio Module

It is not amateur radio by default

Meshtastic is commonly configured for licence-exempt regional SRD/ISM operation. A licensed amateur may use compatible hardware and suitable configurations for experimentation, but amateur-radio privileges and restrictions are a separate legal framework. Meshtastic Introduction Meshtastic Radio Settings

It is not anonymous or perfectly private

The payload may be encrypted, but routing headers remain visible, shared-key security has documented limitations, and radio activity can be observed. Meshtastic Encryption Meshtastic Encryption Limitations

It is not a guaranteed emergency lifeline

Meshtastic has no guaranteed coverage, reserved spectrum, guaranteed delivery, or professional dispatcher. Nodes may be out of range, off, congested, damaged, incorrectly configured, or unable to reach anyone monitoring the channel. Use it as a supplementary tool, not as a replacement for emergency services, properly supported professional radio systems, or certified distress equipment.

Does Meshtastic need the internet?

No. The radio mesh works locally over LoRa without internet access. Meshtastic Introduction

Meshtastic can optionally use MQTT (Message Queuing Telemetry Transport), a lightweight publish-and-subscribe internet protocol, to bridge traffic through an MQTT server. This can connect distant radio meshes, but packets that use the bridge are no longer travelling entirely off-grid. Meshtastic packet metadata can indicate that a packet entered through MQTT, and users can configure whether eligible packets may be uplinked. Meshtastic Technical Overview Meshtastic LoRa Configuration

Read MQTT and internet bridging before enabling a public bridge.

A realistic first experiment

Meshtastic combines long range, low power, and decentralization with strict trade-offs: low data rates, limited airtime, uncertain delivery, imperfect privacy, and coverage that depends heavily on terrain and installation.

To try it:

Confirm the lawful region and frequency band.
Buy compatible hardware for that band.
Install current Meshtastic firmware and a client app.
Keep the default client role.
Select the correct regional preset.
Test with an existing local mesh or a second device.
Improve placement and antenna position before considering more power.

The result is not a private mobile network. It is a community-operated radio path for text, position, and telemetry when ordinary connectivity is absent.