Skip to content

Target Reader

This handbook is for doers — people who are ready to build, not just read.

You don't need to be a networking expert. If you can follow a recipe, you can follow this guide. We assume:

  • Basic computer skills — you can navigate a file system, open a terminal, and aren't afraid of a command line.
  • Willingness to learn — some concepts (IP addressing, VLANs, DNS) will be new. We'll explain them as they come up.
  • A real need — you have a community, school, clinic, or organization that needs connectivity.

You do not need:

  • A computer science degree
  • Expensive equipment
  • A large budget

Who is this for?

Over the years we've handed this kind of knowledge to very different people. Three of them show up again and again — you'll probably recognize yourself in one:

  • The local champion. A teacher, clinic worker, or community member who lives where the network will run. You may not have a technical background, but you're the one who will keep the network alive after the volunteers leave. Start with the story to build a mental model, then lean on the guide when something breaks.
  • The cooperation worker. Someone from an NGO or volunteer organization coordinating a deployment. You need to plan, budget, and explain the project to partners and funders. The story gives you the big picture; the real use cases show how it plays out on the ground.
  • The volunteer engineer. A student or professional with some technical skills, dropping into a project for a few weeks. You want to get productive fast without reading everything. Skim the story, then go straight to the guide recipe you need.

What you'll be able to do

By the time you've worked through this handbook, you'll be able to:

  • Bring an internet connection to a building and spread Wi-Fi across a whole site.
  • Plan an addressing scheme and manage a fleet of routers without losing track of them.
  • Monitor the network so you find out a device is down before a user reports it.
  • Host useful local services and keep them backed up and running.
  • Support the network remotely after you've gone home — and hand it over to a local team that can keep it alive.