# Building a Community Mesh-Network ISP

A community mesh-network ISP starts with a simple premise: neighbors can share infrastructure when the topology is designed for failure instead of perfection. Instead of every subscriber depending on a single provider-owned last mile, rooftop radios, apartment relays, and a few fiber or fixed-wireless uplinks form a distributed access network.

## Network Architecture

Most successful deployments use a hybrid model. The mesh handles local redundancy and short hops, while planned backbone links carry predictable traffic between neighborhoods, data centers, and upstream transit. Subscriber nodes usually bridge Wi-Fi or Ethernet into a small router, while relay nodes run directional 5 GHz or 60 GHz links with clear line of sight.

## Routing and Addressing

Dynamic routing is the core operational difference between a mesh ISP and a normal WISP. Protocols such as Babel, OLSR, or BGP-based overlays let nodes reroute when a rooftop link drops, but metrics need careful tuning so traffic does not wander through weak consumer links.

```ini
interface mesh0
  type wireless
  ssid community-mesh
  encryption sae
  babel_metric 96
```

## Operations

The hard part is not installing radios; it is keeping the network boring. Operators need monitoring, documented mounting standards, spare hardware, firmware rollback plans, and clear ownership rules for customer premises equipment. A small Prometheus and Grafana stack can catch rising packet loss before users experience it as “the internet is slow.”

## Economics

A mesh ISP works best when it is honest about capacity. Shared backhaul, volunteer labor, and donated rooftops can make service affordable, but oversubscription still has consequences. The sustainable model usually combines low-cost residential tiers, paid business service, and transparent community governance around upgrades.