Bootstrapping a New Network

Starting from Zero: Your First Repeater

Every community mesh started with one person who put up the first node. This page is for that person.

The core insight

A community mesh doesn't need to be large to be useful. A single well-placed repeater can cover a neighborhood, a rural township, or a county road corridor - and become the seed that grows a larger network. Start small, start working, and others will join.

The minimum viable network

You can have a functional, useful mesh with just:

A well-placed repeater can cover a surprisingly large area. A rooftop-mounted repeater on the highest building in a small town can, under good line-of-sight conditions, reach much of the town and several miles of surrounding open farmland. Actual coverage varies widely with terrain, obstructions, antenna height, and the receiving nodes — hills, trees, and buildings can shrink it substantially, so treat "covers the whole municipality" as a best case to verify by testing, not a guarantee.

Step 1: Pick your protocol

Before deploying anything, decide which protocol your community will run:

MeshCoreMeshtastic
Best ifJoining an existing regional MeshCore network (CascadiaMesh, WCMesh, RegionMesh, NoDakMesh) or planning a larger community infrastructureStarting fresh with no nearby infrastructure; large global community; simpler initial setup
Check firstIs there existing MeshCore infrastructure in your area? (regionmesh.com — a third-party community site — and cascadiamesh.org; or map.meshcore.io)Are there existing Meshtastic nodes in your area? (meshmap.net — community map, opt-in MQTT nodes only)

Key rule: Join the existing protocol in your area rather than fragmenting the community. Two separate protocols cannot interoperate.

Step 2: Get your first repeater up

The single highest-impact thing you can do is install one good, well-located, permanently-powered repeater. See the Hardware section for build guides. The minimum for a good first repeater:

Step 3: Tell people it exists

A mesh nobody knows about has no community. Before anything else: tell people the repeater exists and how to connect.

What to expect in year one

Growth is rarely explosive. A realistic year-one trajectory for a rural or small-town mesh:

The community builds around real use, not around technology. When people find a genuine reason to use it, they stick with it.

Recruiting Repeater Hosts

The fastest way to grow coverage is to recruit hosts for additional repeaters - people who will let you mount a node on their property. A good host needs to provide: height, power, and patience.

The ideal host profile

Where to find hosts

Amateur radio operators

Ham operators already have antenna infrastructure, understand RF concepts, and are culturally aligned with community communication projects. Local radio clubs are the first call for any mesh network builder. Many hams already have hilltop or tower access and are open to co-locating additional equipment.

Farmers and rural landowners

Rural property owners often want better communication options themselves. A repeater on a grain elevator, water tank, or farm outbuilding benefits the farmer (they get a node) while extending your coverage into underserved rural areas. Frame it as mutual benefit.

Local businesses on tall buildings

Rooftop access to commercial buildings dramatically improves urban coverage. Property managers are more receptive if the installation is visually minimal (a small white antenna on an existing mast) and the equipment is professionally installed. Before any commercial-rooftop install, confirm who actually controls the roof (owner vs. property manager vs. tenant) - a property manager rarely owns the building and is bound by the owner's lease and insurance requirements. Expect to provide a certificate of commercial liability insurance naming the owner as additional insured, sign a roof-access/structural-penetration waiver, and obtain landlord and any HOA/condo-board approval. Antenna or structural changes may also require a local permit.

Fire stations and public works facilities

Many local government facilities are interested in off-grid communication resilience. Fire stations in particular often have tall buildings, 24/7 power, and emergency-preparedness motivation.

Making the ask

The pitch that works best:

  1. Explain what mesh radio is in one sentence: "It's like a community text messaging network that works without cell towers or internet."
  2. Show them the current coverage map and where their location fits in
  3. Offer to handle the installation completely - they don't have to do anything
  4. Describe the equipment: a small weatherproof box, one antenna, and very low power draw (a typical node averages well under 5 watts; continuous transmit is higher but the low duty cycle keeps the average small)
  5. Where budget allows, offering the host their own device can sweeten the ask so they can actually use the network - treat this as a planned, recurring cost (roughly $30+ per device), not a default promise you make to every host

Host agreement basics

Keep it simple but clear. A simple one-page document covering:

Don't over-engineer this for private or residential hosts - most will never look at the agreement again, but having it shows professionalism and prevents misunderstandings years later when personnel change. However, commercial, government, and utility hosts (fire stations, public works, businesses) typically require a formal license or lease plus proof of commercial general liability insurance naming them as additional insured - an informal one-pager will not be enough for those sites.

Naming Conventions and Network Hygiene

Good naming conventions make the network easier to use, debug, and grow. Establish them early - renaming nodes later requires coordinating with the host.

Node naming conventions

Community networks that work well use consistent, descriptive names. The goal: someone who has never seen the network should be able to understand what each node is and roughly where it is, just from the name.

LOCATION-TYPE or LOCATION-DESCRIPTOR

Examples:
OAKHILL-RPTR (Oak Hill, repeater)
DOWNTOWN-RTR (downtown area, router)
SMITH-FARM (Smith Farm, named location)
I90-MP45 (Interstate 90, mile post 45)
N-COUNTY-TOWER (North County tower site)

What to avoid

Network hygiene practices

Document every node

Maintain a simple spreadsheet or wiki page tracking each node:

Monitor for dead nodes

Nodes that go offline and stay offline silently degrade coverage. Set up a monitoring system:

Keep firmware updated

Firmware updates fix bugs and improve performance. For each significant release, update your permanent infrastructure nodes. This requires either physical access (USB) or an OTA update mechanism if your firmware supports it.

Channel and frequency discipline

Every node on your community network must use the same channel and preset. A mismatched modem preset (or region/frequency slot) is a symmetric failure: neither node can decode the other, so a misconfigured node can neither hear nor be heard by the rest of the network - it is not a one-way "can hear but not be heard" situation. Provide new participants with: