Wireless Mesh Network for a Neighborhood

A wireless mesh network for a neighborhood is a set of small radios, usually one per participating household on a roof or in an upstairs window, that relay each other's traffic so the street has a working local network of its own instead of depending entirely on one internet provider. Every node is both a user and a relay. If one goes dark, traffic takes another path.

This page is the build guide: what to survey, what to buy, where to bolt it, who to ask, what it costs and what breaks. The routing theory lives on our companion page, how mesh networks work. Read that to understand the idea. Read this if you have neighbors, a ladder and a weekend.

What You Are Actually Building

Strip away the theory and a neighborhood mesh is a pile of ordinary equipment: a radio at each participating house, something to hold it up, a way to power it, and a cable to a router indoors. The routing that makes it a mesh is software, covered on our theory page. This one is about the parts you screw to a wall.

Most builds land in one of three shapes:

• A long-range text mesh. Small LoRa boards running Meshtastic, one per household, often just sitting in a window. Cheap, slow, tiny power draw, reaches across a whole neighborhood. Messages and sensor readings only.
• A rooftop Wi-Fi mesh. Outdoor Wi-Fi radios on short masts running OpenWrt with a mesh routing protocol. Real bandwidth, shorter hops, needs line of sight, more maintenance.
• Both layers. Wi-Fi between the houses that can see each other, LoRa underneath for the ones that cannot.

Decide the shape before you decide the vendor. The classic mistake is buying gear first, then discovering it cannot see the neighbor it was bought for.

Start With A Sightline Survey, Not A Shopping Cart

The most useful day of the whole build costs nothing. Walk the block with a neighbor and note every high point: rooftops, upstairs windows, chimneys, a flat garage roof, and the tall pine blocking the east side.

Wi-Fi links need to see each other, and they need open air around the straight line between them, not just the line itself. A path that grazes a roof ridge or a hedge will work in the demo and fail in the rain. LoRa forgives obstruction better, but height helps it too. Write down four things as you walk:

• Which pairs of houses can see each other, and at what height.
• Whether the trees are bare today. A link surveyed in February can vanish in May.
• Where mains power already exists near each mounting point.
• Who owns the best roof on the street. Often it is not a member yet.

Then buy two nodes, not ten. Put them on the hardest link on your map and leave them a week before ordering anything else. A survey is a guess; a week of real traffic is evidence.

Choosing Hardware For A Neighborhood Mesh

Buy boring, well-documented hardware. Exotic gear with one forum thread of support becomes a dead node the first time the firmware changes.

Standardize hard. One radio model and one firmware version across the mesh means one set of instructions, one spare in a drawer and one upgrade to test. Mixed hardware is how a volunteer network turns into somebody's unpaid job.

Off-grid LoRa hardware built for this is what Blackout Labs makes. Other suppliers exist; the requirement is the same either way. Documented, repairable, still sold next year.

Mounting, Power And Weatherproofing

Height settles arguments that antenna specifications cannot. A radio a few feet higher on a short mast usually beats a more expensive one at gutter level. Non-penetrating roof mounts, chimney straps and wall brackets avoid drilling through a roof membrane, which matters when the roof is not yours.

Weather is what actually kills outdoor nodes:

• Use outdoor-rated, UV-stable cable. Indoor Ethernet goes brittle in about one summer.
• Leave a drip loop so water runs off the cable instead of into the connector.
• Seal every outdoor connector. Self-amalgamating tape is cheaper than a second ladder trip.
• Ground outdoor mounts, and have a licensed electrician do it. Lightning protection is not the place to improvise.

Power over Ethernet keeps the only outdoor wire a single cable, with the injector indoors next to a small UPS. That one decision lets a node ride out a short outage with no battery on the roof. For nodes that must survive a real grid failure, add a battery and a small solar panel, sized for the worst week of winter rather than an average day. A mesh that dies with the grid solves nothing.

What It Costs And How To Split The Bill

We are not going to quote prices. Radio hardware moves too fast, and a number written today is wrong by the time you read it. The shape of the budget is what stays stable.

• One-time, per node: the radio, an antenna if it is not built in, the mount, outdoor cable, a PoE injector and surge protection.
• One-time, shared: a spare node or two, a ladder or mast if nobody owns one, and the tools.
• Recurring: the internet uplink if you have one, a domain name if you host anything, replacement batteries, and the occasional dead radio.

A LoRa text mesh is the cheapest way to reach a whole neighborhood, rooftop Wi-Fi costs more per house, and the mount and the labor frequently cost more than the radio bolted to them. Budget for the bracket, not just the box.

Split it before you spend it. The pattern that survives: each household buys and owns its own node, and shared items come out of a small pot everyone pays into. Write down who paid for what on day one, while everyone still likes each other. Money and roof access break neighborhood networks far more often than routing protocols.

Permission: Roofs, Landlords, HOAs And The Rules

Ask early, ask in writing, and be specific. Can I mount a small radio on the garage roof, run one cable to my spare room, and take it down if you ask gets a yes far more often than a description of a community network. The list of people to ask:

• Your landlord or building owner, for anything attached to the structure.
• An HOA or condo board, which usually has antenna rules. In the United States the FCC OTARD rule limits some of those restrictions, but it does not cover every antenna or situation, so read the rule rather than a summary of it.
• The city, if you are erecting a real mast rather than a bracket. Height and setback rules are local.
• Neighbors whose wall, view or driveway is involved, even when you are not required to.

On spectrum: ordinary Wi-Fi and LoRa gear runs in unlicensed bands and needs no license, provided you leave the transmit power at the legal defaults for your country. An amateur license permits more power on some bands, but ham rules generally forbid encryption, which rules out most of what a neighborhood network wants to do. Unlicensed is the right answer for nearly everyone.

The Uplink: Sharing One Internet Connection

A mesh moves traffic between its own members with no internet connection at all. Local messaging, a shared file drop, a bulletin board, a map of who needs help on your street: none of that requires an ISP. The moment you want the public internet, somebody's connection becomes the gateway, and that carries different risks.

Three honest problems arrive with a shared uplink:

• Most consumer ISP contracts prohibit sharing or reselling the connection. Read yours before promising the street internet access.
• Whoever hosts the gateway has their name attached to whatever the neighbors do through it.
• One household's connection becomes the slowest part of the network, and the complaints land on them.

The arrangement that lasts treats the uplink as optional. Build so the local services are the point, and let internet access be a shared extra that can be switched off without the network losing its purpose. That is the difference between renting connectivity and owning infrastructure, the whole argument behind data sovereignty.

Maintenance: What Breaks And Who Fixes It

A mesh is a garden, not a monument. Something small needs doing every month, and the network dies quietly when nobody does it. What actually fails, roughly in order: power supplies, batteries in cold weather, connectors that were never sealed, a firmware update that changed a default, and trees. The radio itself is rarely the problem.

A routine that keeps a small network alive:

• Monitor something. Even a plain ping check that alerts you when a node goes quiet beats waiting for a neighbor to mention it.
• Label every node physically and on the map, with an owner's name and an install date.
• Update firmware on one node first, deliberately, and the rest a week later.
• Keep one spare node pre-configured in a drawer. Swapping beats diagnosing on a roof in the rain.
• Re-walk the sightlines once a year, in full leaf.

Then keep the human side written down: who owns each node, who holds the roof key, who pays the uplink, and what happens when a member moves. Groups that record decisions verifiably argue less later, which is why tools like Folkmoot exist.

What A Neighborhood Mesh Will Not Do For You

A neighborhood mesh is genuinely useful and genuinely narrow. Being blunt about the limits is what stops people getting hurt.

• It is not a replacement for your internet connection. It gives you a local network. Streaming, video calls out of state and cloud backups still need an uplink somebody pays for.
• Throughput falls with every hop. A radio cannot receive and transmit at the same instant on the same channel, so each relay costs speed. A few hops out, a link is fine with text and voice and unhappy about video.
• LoRa is not the internet. Meshtastic-class hardware carries short messages a long way. It will not carry a web page, and no setting changes that.
• It is not private by default. Your neighbors relay your packets. Use end-to-end encrypted applications on top. The mesh is a road, not an armored car.
• It needs density and it needs people. Nodes in a straight line cannot route around a failure, and a network with one maintainer has a single point of failure with a pulse.

If you cannot find three committed households, build something smaller and honest: two houses sharing a link, or a LoRa pair that works when the towers do not. Our other guides cover smaller first steps, including reducing what you hand to Big Tech.

Frequently asked questions

How many houses do you need for a neighborhood mesh network?

Three participating households is the realistic minimum. Two nodes make a single link with nothing to fall back on, so any failure splits the network in half. Three or more create a loop, which is what lets traffic route around a dead node. Start with neighbors who already talk to each other, then grow outward.

Do I need permission from a landlord or HOA to mount a mesh antenna?

For anything attached to a building you do not own, yes, and get it in writing. HOAs and condo boards commonly restrict antennas. In the United States the FCC OTARD rule limits some of those restrictions, but it does not cover every case, so read it rather than assume. A removable bracket is an easier ask than a drilled mast.

How far apart can neighborhood mesh nodes be?

It depends far more on what sits between them than on raw distance. Outdoor Wi-Fi links want clear line of sight and typically span rooftop to rooftop across a block or so. LoRa running Meshtastic reaches much farther and tolerates some obstruction, but carries only short messages. Trees, hills and walls shorten everything.

Can a neighborhood mesh network work without internet service?

Yes, and that is often the point. Nodes talk to each other directly, so local messaging, file sharing and any service you host on the mesh keep working with no ISP involved at all. You only need an internet uplink to reach sites and services outside the neighborhood. Build the local side first and add the uplink later.

What hardware works best for a neighborhood wireless mesh?

Two families of gear cover most builds. LoRa boards running Meshtastic handle long-range text and sensor traffic cheaply. Outdoor Wi-Fi radios running OpenWrt with Babel, BATMAN-adv or 802.11s carry real bandwidth between rooftops. Whichever you pick, standardize on one model and one firmware version so a spare node fits anywhere.

How much maintenance does a neighborhood mesh network need?

Plan on a small task every month rather than one big project a year. Power supplies fail, cold weather kills batteries, unsealed connectors let water in, and firmware updates change defaults. Monitor the nodes so you learn about outages automatically, keep one configured spare in a drawer, and re-check sightlines annually when the trees are full.