Ohio Valley Mesh field guide

How OVMesh Works

Small nodes use LoRa radio signals to move messages across valleys, ridges and towns without depending on cell service or the internet. OVMesh supports Meshtastic today and is preparing regional support for MeshCore.

The big picture

Shared terrain. Different routing.

Both platforms send compact data packets over long-range, low-power radio. What differs is how devices discover paths, which nodes forward traffic and how conversations are organized.

Current OVMesh network

Meshtastic

Most users carry Client nodes. Compatible nearby nodes may rebroadcast packets according to their role and the managed-flood routing rules, allowing a message to travel across multiple radio hops.

Every node has numbered places for channels. On OVMesh, the shared public channel uses the LongFast radio preset in the Channel 0 slot. Private group channels can be added in the remaining slots.

Early regional rollout

MeshCore

MeshCore user nodes normally run Companion firmware and do not relay other users’ traffic. Dedicated Repeaters form the forwarding layer, while optional Room Servers can hold channel posts for later retrieval.

OVMesh is beginning a regional MeshCore rollout alongside the established Meshtastic network. Companion nodes are welcome. Permanent Repeaters and Room Servers should be coordinated through the OVMesh Discord.

No tower or internet requiredLocal LoRa paths work without cellular infrastructure, Wi-Fi or an internet connection.
Placement mattersA clear elevated path usually contributes more than raw transmit power.
Delivery is best effortTerrain, congestion, interference and changing paths can still prevent a packet from arriving.

From send to receive

Two message journeys

The experience can look like a familiar chat app, but the packet is moving by radio. These simplified journeys show what happens underneath.

Meshtastic

Public regional messaging with optional private secondary channels.

  1. You compose a message.A phone connects to the node by Bluetooth, USB, or Wi-Fi where supported. You can also use a standalone node with its own controls.
  2. Your node creates a LoRa packet.The packet uses the regional radio settings and the selected channel. Internet access is not required.
  3. Nearby compatible nodes may rebroadcast it.Clients and planned infrastructure roles follow Meshtastic’s rebroadcast rules, suppressing duplicate traffic and sharing limited airtime.
  4. The packet crosses a bounded number of hops.OVMesh currently recommends a maximum of five hops. More hops consume more shared airtime and are not automatically better.
  5. The receiving node delivers it.A matching channel key allows the device to decrypt and display the message. Acknowledgements can provide useful delivery evidence, but are not a guarantee.

MeshCore

Companion devices use a dedicated regional repeater layer.

  1. You compose a message in a Companion app.The phone or computer is the interface; the attached Companion node handles the LoRa link.
  2. The Companion selects or discovers a path.Network advertisements and path discovery help the device learn which Repeaters can reach the destination.
  3. Dedicated Repeaters forward the packet.Companion nodes do not repeat other users’ traffic. Fixed Repeaters provide the routing infrastructure.
  4. The destination receives the encrypted payload.MeshCore supports direct messages and channel conversations. Only intended participants should have the necessary keys.
  5. A Room Server can add persistence.Users can retrieve channel posts from a Room Server after reconnecting. OVMesh plans to keep room and repeater functions on appropriately designed infrastructure.

Ohio Valley reality

The landscape shapes the network.

LoRa can travel impressive distances with a clear path, but hills, buildings, foliage and radio noise matter. Coverage grows through deliberate placement, not simply by adding more radios.

Valley nodes

Serve local neighborhoods and may need a clean path to a hillside or ridge site before they can reach the wider region.

High sites

A well-placed attic, hillside or ridge node can bridge areas that cannot hear each other directly.

Good RF practice

A tuned antenna, useful height, low-loss feed line and distance from noisy electronics often produce the largest gains.

More than chat

What can move across the mesh?

These are low-bandwidth networks. Short, useful updates are a good fit; photos, voice calls and large files are not.

Messages

Public community chat, direct messages and private group conversations, depending on the platform and channel configuration.

Position

Optional location updates for coordination and mapping. Share only the precision appropriate for the audience.

Telemetry

Battery, voltage, temperature, humidity, pressure, air quality and other sensor data at airtime-conscious reporting intervals.

Network responsibilities

User nodes and infrastructure

Choosing the correct role protects shared airtime. A role intended for planned infrastructure should not be treated as a performance upgrade for a handheld node.

Meshtastic roles

ClientThe right default for most handheld and general-purpose OVMesh nodes; participates in managed rebroadcasting.
Client MuteUses the network without relaying other nodes’ packets.
Client BaseA strong personal fixed node that can prioritize traffic involving favorited personal nodes.
Router / Router LatePlanned regional infrastructure only. Coordinate with OVMesh before deploying these roles.

MeshCore roles

CompanionThe user-facing node connected to the app. It sends and receives but does not repeat network traffic.
RepeaterDedicated forwarding infrastructure that extends message paths between nodes and other repeaters.
Room ServerStores channel posts for later retrieval and can support persistent community rooms.
Regional deploymentThe initial OVMesh configuration is established. Meshtastic remains the primary regional network while dual-radio MeshCore coverage is introduced. Coordinate permanent Repeaters, Room Servers and other shared infrastructure through the OVMesh Discord before deployment.

Technical references: Meshtastic routing, Meshtastic roles, MeshCore documentation, and the OVMesh FAQ.

Build useful coverage

Start with the current OVMesh network.

Configure a Meshtastic Client on the public regional channel, test from a practical location and join the community before planning fixed infrastructure. OVMesh has begun introducing MeshCore alongside the primary Meshtastic network. Companion nodes are welcome; coordinate permanent infrastructure through the OVMesh Discord before deployment.

Set up MeshtasticJoin the community