Planning Your Network

Is There Already a Network in Your Area?

Is There Already a Network in Your Area?

Before starting a new mesh network, check whether an existing network already covers your area. Joining an established network is almost always better than starting from scratch - you immediately have more repeaters, a larger community, and tested infrastructure.

How to Check

Live Node Maps

Existing Networks by Region

RegionNetworkWebsite
Nationwide USRegionMeshregionmesh.com
North Dakota & surroundsNoDakMeshnodakmesh.org
West CoastWCMeshwcmesh.com
Pacific NorthwestCascadiaMeshcascadiamesh.org

If No Network Exists

If you genuinely can't find an existing network in your area, you have the opportunity to start one. A few considerations:

Choosing Your Protocol and Channel

Choosing Your Protocol and Channel

The two dominant LoRa mesh protocols for community networks are MeshCore and Meshtastic. They are not interoperable - nodes must use the same protocol to communicate.

Protocol Comparison

FeatureMeshCoreMeshtastic
Infrastructure modelDedicated repeaters + companion nodesPeer-to-peer; any node can relay
Room serversYes - built-in store-and-forwardNo full equivalent (an optional Store & Forward module on a PSRAM node is a partial analog, not a room-server/bulletin board)
MQTT gatewayCommunity brokers (e.g. letsmesh.net, meshmapper.cc)Official public broker (mqtt.meshtastic.org)
Regional scopingYes - operator-defined region labels (lowercase alphanumeric + hyphen, max 29 bytes) hashed to 2-byte transport codes; no official registry or ISO standardNo
AppMeshCore companion appMeshtastic app (iOS/Android)
Hardware compatibilityCommonly ESP32 and nRF52840 boards with SX1262 radio (e.g. Heltec V3, RAK4631, T114, T-Beam); some SX1276 boards are also supported. Verify the current board list at flasher.meshcore.io / docs.meshcore.io.ESP32 and nRF52 boards
Large existing networkRegionMesh (a growing national MeshCore network; see the live map at regionmesh.com for current coverage)Meshtastic worldwide (meshmap.net, a community map - the official map link is on meshtastic.org)

General Guidance

Channel Selection for MeshCore

Most North American MeshCore networks use the USA/Canada preset: 910.525 MHz / 62.5 kHz BW / SF7 / CR5 (as of 2026-06). This is the default for RegionMesh and many other communities; confirm current settings with your local network before deploying, as presets are periodically revised.

If your area has a pre-existing local MeshCore deployment on different settings, match those settings to join that network. Check locally first - then default to the USA/Canada preset.

Channel Selection for Meshtastic

Do not use a custom channel key unless your community has a specific reason to create a private channel. Using the default key ensures maximum interoperability with travelers and other local nodes.

Setting Channel Keys and Network Identity

Your channel configuration defines who can communicate on your mesh. Getting it right from the start saves painful re-configuration later as your network grows.

Understanding Channel Keys

Both Meshtastic and MeshCore use a shared channel key (Pre-Shared Key or PSK) that all nodes on a given channel must share to communicate. The key serves two functions:

Important: If you use the Meshtastic default key ("AQ==", which is base64 for the single byte 0x01 - the publicly known default key, not "all-zeros"), the firmware expands it into the well-known default PSK and your messages are readable by every Meshtastic node in range. For a community network, always set a custom channel key.

Generating a Strong Channel Key

Meshtastic channel encryption uses AES-256-CTR when a 32-byte (256-bit) key is used. Custom PSKs can be 0, 128-bit (16 bytes), or 256-bit (32 bytes). Generate a strong 256-bit key:

# Generate a random 256-bit key (32 bytes, base64 encoded)
python3 -c "import os, base64; print(base64.b64encode(os.urandom(32)).decode())"

Distributing Channel Keys

Methods for sharing your channel key with new members:

Key distribution security: Your channel key doesn't need to be secret from trusted community members, but don't publish it on your public website. Share it in your community Discord/Signal or at in-person events.

Multi-Channel Strategy

Consider running multiple channels for different purposes:

Channel NameKeyPurpose
Community-PublicPublished freelyGeneral community chatter, newcomer welcome
Community-OpsMembers onlyNetwork operations, node status updates
EmCommEmergency teams onlyYour group's own coordination and drills (see caveat below)

EmComm channel caveat: A private "EmComm" channel is fine for your own group's coordination and drills under unlicensed Part 15 (915 MHz ISM) operation, but it is not a substitute for authorized public-safety or amateur-radio emergency channels. Two limits apply: an encrypted channel cannot be used by stations operating under amateur radio (Part 97), which prohibits messages encoded to obscure their meaning; and formal ARES/RACES/served-agency traffic must stay on authorized, often monitorable channels. During a real activation, follow your served agency's and ARES/RACES communication plan rather than relying on a private encrypted hobby-mesh channel.

Network Name and Node Naming Conventions

Establish naming standards early. Consistent naming makes the node list immediately informative:

Infrastructure Agreements and Permissions

Getting your repeater or backbone node onto high-elevation infrastructure dramatically improves coverage - but it requires agreements with property owners. (High-elevation, line-of-sight siting is core Meshtastic guidance; see the Meshtastic siting tips.)

Types of Infrastructure Sites

The best sites for backbone nodes (roughly in order of typical access difficulty):

  1. Your own property - On property you own you generally need no third-party agreement, but it is not automatically unrestricted: check HOA covenants, local zoning/permit rules for antenna masts, and (if you rent, or for a friend's house) the applicable lease. Start here: your house, or a friend's house with a tall tree or roof peak.
  2. Amateur radio repeater sites - Existing ham radio clubs often have hilltop sites with tower space, power, and sometimes internet. Approach club leadership to discuss hosting. Note: default Meshtastic runs in the license-free 902-928 MHz ISM band (Part 15), where there is no ham frequency coordination and encryption is allowed. Formal ham-frequency coordination only applies if you operate in HAM mode under Part 97 (licensed, and encryption is not permitted) - clarify which regime applies before discussing "frequency coordination."
  3. Commercial buildings - Restaurants, shops with flat roofs. Pitch: "We're a community communications nonprofit. We'd like to install a small weatherproof box the size of a paperback book on your rooftop. No wiring to your building, runs on its own battery/solar." Expect the owner to ask for proof of commercial liability insurance naming them as additional insured (see Insurance Considerations below).
  4. Municipal property - Parks department, public works, and fire departments sometimes allow installations for emergency-preparedness benefit, but expect a formal license/use agreement requiring proof of commercial liability insurance (municipality named as additional insured), an indemnification clause, and sometimes risk-management or council approval - not just an informal MOU. Highly jurisdiction-dependent.
  5. Water towers - Managed by municipal water utilities, and among the highest-liability, hardest-to-permit sites. Utilities universally require commercial general liability insurance naming the utility as additional insured, a formal site/license agreement, and often background checks and trained climbers, because access involves fall hazards and potable-water security. Do not treat a water tower as an informal site.
  6. Cell towers - Carrier-grade macro tower and managed-rooftop colocation typically runs $1,000-$3,000+/month (urban higher); small-cell sites run roughly $100-$250/month. More importantly, many tower operators will not lease space for a device this small at any price - treat commercial tower colocation as a last resort. Amateur-radio repeater sites and municipal buildings are far more accessible.

What to Include in a Site Agreement

Even for informal arrangements, a simple one-page written agreement protects both parties:

Insurance Considerations

Most institutional partners will ask whether you carry liability insurance. Coverage scope varies - confirm specifics with a licensed agent before relying on any policy. Options:

Maintaining Relationships with Site Hosts