How to Plan a Public Meshtastic Network

A public Meshtastic network should be designed as a service shared by a community, not as a random collection of personal radios. Good planning identifies who should be reached, where radio paths are possible, which sites can be maintained and how nodes will share scarce airtime.

1. Define the purpose and boundary

Begin with a map and a short written objective. List the settlements, roads, trails, facilities and event spaces that matter. Identify the expected users: residents, hikers, radio amateurs, volunteers, businesses or visitors. Decide whether the first phase is neighborhood coverage, a town-wide network or a connection between two existing groups.

Do not promise emergency-grade communication unless the organization, power system, maintenance and testing genuinely support that claim. Meshtastic can be valuable when mobile networks are overloaded or absent, but a volunteer public mesh is not automatically a certified emergency service.

2. Inventory what already exists

Use public node maps, local groups and direct listening to identify active nodes. A map icon does not prove that a node is currently operating, reachable from the ground or configured compatibly. Record when it was last heard, its advertised role and whether its owner is available.

Also inventory reusable infrastructure: radio-club towers, internet-provider sites, farms, hotels, mountain huts, municipal buildings and private roofs. Existing power, grounding, mast space and site access may be more valuable than an additional radio board.

3. Read the terrain

Draw likely paths between candidate sites. Mountain ridges can provide exceptional coverage but can also divide valleys completely. In towns, reinforced concrete and the clutter of roofs create local shadows. Trees become more lossy when wet and seasonal vegetation can change a path that worked in winter.

Prefer a few sites with clear views over many sites installed low indoors. For a regional backbone, look for locations that see two or more coverage areas. For neighborhood access, place antennas where normal handheld nodes can answer—not only where a powerful base station can be heard.

4. Design coverage layers

Layer	Purpose	Typical site
User access	Reach people in homes, streets and trails	Roof, window, small hill
Local distribution	Connect neighborhoods or parts of a valley	Tall building, ridge shoulder
Regional backbone	Join separate coverage areas	High ridge, tower, prominent summit
Gateway and monitoring	Optional internet bridge and operational visibility	Powered site with reliable backhaul

Not every community needs every layer. A compact town may work well with two complementary rooftop sites. Mountainous territory may require a high backbone node plus lower sites that reach streets and valleys.

5. Choose a common configuration

Agree on the legal region, LoRa modem preset, frequency slot, primary public channel and naming scheme. Most user nodes should remain CLIENT. Assign infrastructure roles only after understanding their rebroadcast behavior. Keep the normal hop limit at three unless testing demonstrates a specific need; the official Meshtastic configuration tips warn that unnecessary hop counts cause network problems.

Set conservative position, node-information and telemetry intervals. Airtime is shared by every participant on the same radio settings, whether or not they can decrypt a packet. Avoid turning a public network into a constant stream of status data.

6. Test before permanent installation

Temporarily place radios and antennas at candidate sites. Test from representative streets, buildings and roads rather than from one unusually favorable point. Confirm both directions: an elevated node may reach a handheld that lacks enough link budget to answer reliably.

Record packet delivery, RSSI, SNR, antenna type, height, weather and exact test position. Meshtastic’s Range Test module can automate sequential packets and CSV logging, but disable it after testing because repeated test traffic consumes airtime.

7. Select sites by total value

Compare radio value with practical sustainability. A slightly lower building with permanent power, safe access and an engaged host may outperform a perfect summit that can only be visited twice per year. Obtain written permission and agree on mounting, electricity, access, liability and removal.

8. Add redundancy deliberately

Identify which single failure would split the network. Add an alternate path around that cut, ideally using a different site, power source and access route. Redundancy is not two radios in the same wet enclosure or two sites on the same building supply.

9. Establish operations before launch

Give every node a steward and an installation record. Store configuration backups, firmware version, photos, antenna and cable details, battery information, host permission and maintenance history. Define who may change shared settings and how changes are announced.

Publish enough information for users to understand coverage while protecting private hosts. Approximate coordinates are usually sufficient for private rooftops; the operations team can retain exact details securely.

10. Expand from measured demand

After the pilot runs for several weeks, review gaps, congestion and failures. Add a node only when it solves a named problem: a shadowed neighborhood, a weak inter-town path, missing redundancy or a user cluster. A quieter mesh with six well-placed nodes can be more useful than a noisy mesh with sixty poorly configured ones.