COWMesh

COWMesh (Community-Owned and/or Operated Wireless Mesh)

Overview

COWMesh is an approach to building community-owned and/or community-operated wireless mesh networks using low-cost, open technologies. It focuses on decentralised ownership of communication infrastructure, enabling communities to deploy, manage, and sustain their own networks based on local needs.

The model emphasises:

• Local control over infrastructure
• Use of unlicensed wireless spectrum
• Open-source firmware and tools
• Community-led deployment, maintenance, and governance

COWMesh networks support both internet access and locally hosted services such as archives, media sharing, and learning systems.

Design Philosophy

COWMesh deployments are guided by the following principles:

• Community Ownership – Infrastructure is collectively managed and maintained by the community
• Decentralisation – Distributed mesh topology with no single point of failure
• Low-cost & Repairability – Preference for locally available, replaceable components
• Transparency – Use of open-source software and understandable configurations
• Context-driven Design – Adaptation to terrain, culture, and use-case

Evolution of Technology Stack

Early Deployments

Initial deployments used:

• LibreRouter
• LibreMesh firmware on supported TP-Link hardware

LibreMesh provided a pre-configured mesh stack for rapid deployment.

Limitations observed:

• Hardware Availability – LibreRouter is not easily available in India and is not cost-effective
• Limited Flexibility – Pre-configured nature of LibreMesh made it difficult to adapt configurations
• Operational Constraints – Customising routing, services, and topology was restrictive

Transition to OpenWrt

Deployments transitioned to:

• Commodity TP-Link routers and other locally available hardware
• OpenWrt with manual configuration

Advantages:

• Full control over configuration
• Flexible routing protocol selection (e.g., Babeld)
• Easier scaling using locally available hardware
• Better alignment with diverse community requirements

This transition enabled a shift towards **from-scratch, context-driven network design**.

Network Architecture

Typical COWMesh deployments include:

• Backhaul Links – Long-distance wireless links to upstream connectivity
• Mesh Layer – 802.11s-based mesh with dynamic routing
• Access Layer – Wi-Fi access points for end users
• Local Infrastructure – Community-hosted services and monitoring systems

Design is dependent on:

• Line-of-sight (LoS) conditions
• Terrain and settlement patterns
• Power availability
• Community requirements

Power Systems and Infrastructure

In many deployments, reliable grid power is unavailable or unstable. COWMesh networks therefore use decentralised power systems.

Components

Typical node-level infrastructure includes:

• Solar panels
• Solar PWM charge controllers
• Battery banks
• DC power distribution
• Outdoor-rated Ethernet cables
• Metal poles and mounting clamps
• Weatherproof outdoor enclosures

Each node is designed to operate independently, enabling resilience and fault isolation.

Community-Manageable Power Design

1. Locally Repairable Systems

A core principle is that the network must be maintainable by the community without reliance on proprietary systems.

Industrial outdoor power systems:

• Are expensive
• Use proprietary components
• Are difficult to repair locally

To address this:

• Locally available materials are used
• Power systems are designed for simplicity and repairability
• Components can be replaced or fixed using local skills

This approach increases deployment time but ensures long-term sustainability and autonomy.

2. Protective Enclosures for Field Conditions

Deployments operate in harsh outdoor environments with significant wildlife interaction.

Custom enclosures are designed to be:

• Animal-proof – Resistant to monkeys and squirrels chewing cables
• Insect-proof – Prevent ants and insects entering equipment
• Weather-resistant – Suitable for rain and monsoon conditions
• Locally repairable – Built using materials available in nearby markets

These enclosures house:

• Batteries
• Charge controllers
• Power distribution units

Development involved multiple iterations and field testing.

3. Iterative Field Engineering

Due to the use of low-cost hardware and local materials, deployments involve continuous experimentation.

Observed challenges:

• Routers damaged due to unstable early power setups
• Solar systems requiring redesign for load and environmental conditions
• Failures caused by rain, wildlife, and component limitations

This trial-and-error process led to:

• Improved power stability
• More robust enclosure designs
• Better long-term reliability

Community Participation

COWMesh deployments are implemented collaboratively with community members.

Key practices:

• Hands-on involvement during installation
• Training in:

 * Networking fundamentals  
 * Router installation and alignment  
 * Cable preparation and electrical safety  
 * Basic troubleshooting  

• Identification of local operators for ongoing maintenance

This ensures continuity and reduces dependence on external technical support.

Field Constraints

Common constraints influencing deployments:

• Terrain and lack of line-of-sight
• Limited availability of hardware and materials
• Power instability
• Environmental exposure
• Wildlife interference
• Administrative and access constraints

These factors shape both technical design and deployment timelines.

Conclusion

COWMesh represents a shift from connectivity as a service to **connectivity as community-owned infrastructure**.

By combining:

• Open wireless technologies
• Locally sourced hardware
• Community participation

it enables resilient, adaptable, and locally sustainable communication networks.