Durham, NC | 24 April 2026

There’s a moment in a lot of mutual aid work where something shifts, and if you weren’t there for it, you might never even know it happened.

There’s no announcement, no press release, no clean “before and after.” It’s usually just a handful of people showing up, carrying what they can, figuring it out as they go, and trusting each other enough to try something that isn’t guaranteed to work.

For us, that moment probably started back in January.

Triangle Mutual Aid hosted an open “mesh interest” meeting, and going into it, the expectation was pretty modest — maybe half a dozen people, a few radios on the table, a conversation that might or might not go anywhere. Instead, it was a standing-room only. People packed into the space, not just radio folks, but organizers, community members, people trying to understand what it would mean to have communications that didn’t depend on the same infrastructure we’re all used to relying on.

At that point, I was a MeshCore newb, but something was clearly happening.

After the meeting, I went home, flashed my first node, and within a day or two I had maybe eight contacts, just a short list of names, enough to prove that the thing actually worked. A few months later, that list is maxed out. Same network, same basic idea, but it’s grown into something that feels alive. More nodes, more paths, more reasons to use it, more people taking ownership of it in their own way.

That meeting didn’t just introduce a piece of technology. It introduced a group of people who were willing to build something together.

That’s where I met Magnus, a mesh enthusiast out of Raleigh who had already been putting time into getting things organized locally. He registered rdumesh.org early on, and has been one of several people helping keep things moving, connecting folks, sharing information, and doing coordination work that doesn’t really show up on a map. A lot of that effort is quiet, and it’s spread across a handful of people who have been steadily building momentum in the Triangle and beyond. That behind-the-scenes work is what makes something like this possible before there’s ever a clear plan for it.

The Opportunity

From there, things moved the way they usually do in mutual aid spaces. There was no formal rollout, but relationships that were already in place got levered, and one conversation after another opened the door to an opportunity: access to a rooftop on UNC Chapel Hill’s campus, twelve stories up, already home to infrastructure that carries a lot of importance — the NC VIPER radio system, the college’s microwave audio link, a Chapel Hill Fire Department repeater – a site where communications isn’t abstract but mission critical.

It’s also not the kind of place you get access to just by asking.

That path ran through my teammate Chris Cardwell with NC Task Force 8 and captain at Chapel Hill Fire, who was willing to make space for something new to sit alongside their tried and true. That piece matters, because this wasn’t something happening off to the side, and it wasn’t something being absorbed into a larger system either. It sat somewhere in between. It was a bridge. And once that door opened, people showed up to build that bridge.

Carrying the Network Up

There’s no version of this where you order everything from one place and it arrives ready to install.

What went up to that roof came from all over, and it came together because people brought what they had.

Magnus contributed hardware. lbibass handled integration work, including pieces that only exist because they took the time to design and 3D print them. Triangle Mutual Aid stepped in and covered the cost of a commercial 900 MHz antenna. It’s not the kind of thing that draws attention, but exactly the kind of thing that determines whether an effort like this actually performs.

I brought a couple of pieces too, and each of them had their own path into the build. A 915 MHz bandpass filter, sourced from another builder (shout out @nullrouten on Discord) shipped up from Georgia. It’s a component that most people will never notice but that makes a real difference when you’re sitting in a crowded RF environment surrounded by high-powered systems.

And then there was the 10-foot pole, something I insisted on bringing in order to eke out the most height possible on top of that roof. The pole was passed along through the local amateur radio community by Fin Gold (NC4FG) with the Raleigh Amateur Radio Society. That pole turned out to be a little more memorable than expected. It didn’t fit in the elevator, so I knew I had to carry it up the stairwell. All twelve stories of it. Everyone else took the elevator so it was my burden alone. There was a point somewhere in the middle of that climb where it stopped being a minor inconvenience and started to feel like one of those tests of whether you’re actually going to finish what you started. But that’s also kind of what this work is, you don’t always get the easy version, and there isn’t really another option besides continuing to put one foot in front of the other until you get where you’re going. By the time that pole made it to the roof, it felt like nothing was going to stop this project from happening.

Individually, none of those pieces would have done much – they’re just parts. Together, they became community infrastructure.

When It Came Online

There’s no dramatic moment when a node comes online. You don’t throw a switch and watch the horizon light up. It’s quieter than that. On discord, lbibass shared a hop path with a map layer behind it. Other indicators started to show as well.

At first, the impact was local. Chapel Hill stopped feeling like the edge of the network and started behaving like a real part of it. Paths appeared where there weren’t paths before, and nodes that used to sit just out of reach (“islands”) suddenly had somewhere to go.

And then, after a little while, something else started to show up. Paths that weren’t the original goal. A clean, stable hop to the west – particularly to Cane Mountain in Alamance County. One link becomes another, and another after that, and before long it’s clear that what came online wasn’t just a way to connect Chapel Hill to Durham or Raleigh — it was a path reaching out toward western North Carolina, and beyond that into Tennessee, Kentucky, Georgia, Virginia.

That wasn’t the headline going into it, but it’s one of the most important things that came out of it. Because at that point, we weren’t just talking about local coverage anymore. We’re talking about regions. We’re talking about the ability for information to move across distance without depending on the same centralized systems that tend to fail in the same ways, at the same times. We’re talking about a different kind of resilience.

Mutual Aid as Infrastructure

A lot of the time, mutual aid is framed around response, showing up when something breaks, filling a gap, meeting a need in the moment.

But there’s another layer to it that doesn’t get talked about as much. It’s the work of building things ahead of time, in ways that make those moments less fragile when they come. I think that’s what this is. Tarheel Backhaul isn’t just a repeater on a tall building. It’s part of a communications system that doesn’t depend on a monthly bill, doesn’t require permission to use, and doesn’t disappear just because a centralized network is overloaded or censored or unavailable. And now it’s part of a path that connects not just neighborhoods or cities, but regions. It exists because people built it, and it works because people keep participating in it.

That’s a different model of infrastructure, one that’s based on relationships instead of transactions.

Closing

That meeting in January could have just been yet another tech meet-up. Instead, it became the starting point for something that now stretches across cities, across regions, across state lines. The rooftop in Chapel Hill is part of that story, but it isn’t the whole thing. The whole thing is that people showed up, and then kept showing up, and kept building, and kept connecting what they had to what other people had already put in place. There wasn’t a single moment where it all came together. But somewhere along the way, it did. And now Chapel Hill is on the mesh.

1: What will the repeater node be used for?

• It will expand a community oriented, free, open source community mesh network using low power radio
• The mesh enables text-based communication in areas with limited cellular or internet coverage, or to users who can't afford cellular or internet service
• It stays up when power, cellular networks, or the internet goes down, enabling emergency communications and community support

2: What kind of equipment will be installed?

• Normally a small, waterproof box containing a microcontroller and a battery
• A lightweight antenna and a small solar panel or two
• Typically under two pounds, about the size of an internet router with a larger antenna

3: How much power and bandwidth are required?

• None. Nodes are intentionally self sufficient; they are solar powered and do not connect to the internet

4: How will it be installed?

• Installation on structures normally uses magnets on a flat metal surface or u-bolts/hose clamps around a mast or pole.
• Installation in trees normally uses a small rope around a sturdy branch, with the node hanging from below, and a longer rope used to hoist the node in place (like a flagpole).
• No screwing, nailing, drilling, or adhesives are used unless explicitly agreed on beforehand.
• If you have specific requirements, let us know. We can almost always find a way to complete installation without requiring any alteration to your property, provided that the solar panel(s) are exposed to the sun.
• Depending on the circumstance, a cable may be run between the node and the antenna. No cabling will be run into the structure.

5: What is the expected maintenance/access requirement?

• Very low; nodes are designed to run autonomously for long periods
• Occasional visits may be needed for firmware updates or hardware checks/maintenance, typically no more than once or twice a year.
• Access terms can be agreed on and set in writing

6: Will the equipment cause any interference with my existing systems?

• Extremely unlikely; the RDUMesh network operates on different frequencies from Wi-Fi, cellular, or TV systems (specifically the ISM band, 902-928 MHz)
• Transmit power does not exceed 1 watt; typically 0.3-0.6 watts
• Nodes are designed to be non-disruptive and FCC compliant; you can request testing or documentation if concerned

7: What are the security risks for my network/customer data?

• Virtually non-existent; nodes will not connect to your network/wi-fi in any way
• Most nodes do not have wi-fi radios at all; those that do have them disabled except during firmware updates, and they do not connect to other networks for updates. We can accommodate requests for nodes with no wi-fi capabilities if needed
• Nodes typically have low power bluetooth radios, but these are also disabled except during firmware updates
• Nodes do not have cameras or sensors, except for temperature and voltage sensors used to monitor the node's own hardware.
• Nodes do not broadcast their own messages except to advertise their presence or report their temperature or battery level; they only repeat messages from end-user devices.

8: What are the liability implications?

• The property owner carries the liability, although the likelihood of an incident is expected to be minimal

9: Are there any permits, HOA, zoning, or regulatory issues to be aware of?

• Permits are not needed for small antennas or non-commercial installations
• HOA or building rules may restrict roof modifications, even non-permanent ones - check before proceeding
• We recommend getting written permission if you're a tenant or part of a shared property

10: What is the day to day experience like?

• If you choose to use the mesh, you'll benefit from a reliable link to the network
• Otherwise, you'll probably forget that it's there. Nodes are designed to function autonomously for long periods with no in-person interaction and don't need anything other than elevation and sunlight.

11: How long is the node expected to stay there? Can it be removed at any time?

• We will work with you to determine a clear agreement or time frame
• No long-term obligation is required. Ultimately, you may request removal at any time, with coordination and reasonable time allowance for removal
• Removal should not leave any long term marks or damage

Credit to Austin Mesh for much of the formatting and content

Welcome! This page is meant to get you up and running quickly, with critical settings where needed and sensible defaults everywhere else.

1: Open Edge or Chrome and go to https://flasher.meshcore.io/. Firefox won't work here.

2: Search for your device by name. If you're not sure, you can hover your mouse over the device name to see a picture. Click on the correct device.

3: Choose the role for your device:

4: Click "Enter DFU Mode" if it is displayed.

5: If this is the first time you've flashed this device, click "Erase Device" or "Erase Flash"

6: When this has finished, click "Flash!"

7: Select follow-up instructions based on your device role

Comprehensive MeshCore FAQ - Beginner to Advanced

Building a Resilient Off-Grid Mesh Network in Central North Carolina

Welcome to RDUMesh! This comprehensive guide covers everything you need to know about building and using the MeshCore mesh network in the Raleigh-Durham-Chapel Hill (Triangle) area of Central North Carolina and eventually extending it out to all counties serviced by the RDU airport.

MeshCore is an open-source, off-grid mesh network system that enables secure text messaging using LoRa radios operating on the 915 MHz ISM band - no licenses, internet or cell service required.

Critical: RDUMesh uses MeshCore, not Meshtastic. These are different systems with different architectures. Some key differences: In MeshCore, companion nodes (personal devices) do NOT repeat messages. Only repeater nodes relay traffic. Messages can be repeated by up to 64 nodes to get to where they need to be. This planned infrastructure approach creates a more reliable, scalable network.

Our Philosophy: RDUMesh is designed to work when the internet and power grid fail. We do NOT use the internet to interconnect nodes that couldn't otherwise connect via RF. If we have connectivity problems, we solve them with better repeater placement and RF solutions - not internet backhauls. The mesh must be resilient and independent.

Table of Contents:

•      Part 1: Getting Started with MeshCore

•      Part 2: Hardware Recommendations

•      Part 3: Antenna Selection and Configuration

•      Part 4: Height is Might - Elevation Strategies

•      Part 5: Wardriving and Network Discovery

•      Part 6: How to Help the Community

•      Part 7: Privacy and Anonymity - The Reality

•      Part 8: Advanced Topics and Network Strategy

PART 1: Getting Started with MeshCore

Q: What is MeshCore and how is it different from Meshtastic?

A: MeshCore is an open-source mesh networking and communication system using LoRa (Long Range) radio technology on the 915 MHz ISM band in the United States. Here's what makes it different:

•      Planned Infrastructure: MeshCore requires dedicated repeater nodes for network coverage beyond the range of a single node. Companion nodes (personal devices) do NOT repeat messages*(1) - they only send and receive on behalf of their owner. This prevents network flooding and collisions.

•      Higher Hop Limits: MeshCore currently supports up to 64 hops (versus 3-7 in Meshtastic), enabling messages to traverse larger geographic areas, assuming proper repeater placement.

•      Efficient Routing: MeshCore uses hybrid flood-then-direct routing. Initial messages flood to discover paths, then subsequent messages use known routes for efficiency.

•      Lower Telemetry Overhead: MeshCore minimizes unnecessary telemetry traffic, conserving bandwidth for actual messages.

Bottom Line: MeshCore is designed for planned, scalable mesh networks with fixed repeater infrastructure - ideal for covering regions like the 16 counties served by RDU airport.

Q: What are the different types of MeshCore devices?

A: MeshCore has distinct firmware types for different roles:

•      BLE Companion: A personal device that connects to your smartphone via Bluetooth. You carry this for messaging. Companions do NOT repeat messages for others*(1) - they only send and receive your own communications. This is likely what you'd want first to get started. If you're going to keep your companion mobile, consider blanking its location as to not confuse the mesh when you're clearly not where you say you are.

•      Repeater: Stationary infrastructure nodes placed at high elevations that relay messages across the network. These are the backbone of the mesh and should run 24/7.

•      Room Server: A store-and-forward message server that holds messages for offline users and delivers them when they reconnect. Can also act as a repeater.

•      Ripple GUI, MeshOS, Others with a GUI : Standalone devices (like T-Deck/T-Deck Plus) with screen and keyboard - complete messaging devices that don't require a smart phone like the BLE companions.

Key Point: Unlike other systems, MeshCore companions do NOT participate in routing. This is by design to mitigate network congestion.

Q: How do I flash MeshCore firmware to my device?

A: Use the MeshCore Web Flasher:

•      Step 1: NEVER power on your device without an antenna attached! This can permanently damage the radio chip.

•      Step 2: Open Chrome or Edge browser (required for WebUSB) and go to: https://flasher.meshcore.co.uk

•      Step 3: Connect your device via USB cable (verify it's a data cable, not charge-only).

•      Step 4: Select your device type and firmware role (BLE Companion for personal devices, Repeater for infrastructure). Decide whether you aant to fully erase the device before flashing. Erasing is good if this is the first time you're flashing the device. It'll clear out any settings from a previous firmware. If you're upgrading your firmware and want to keep your existing identity/settings, DO NOT erase.

•      Step 5: Figure out which serial device yours is. You may benefit from cycling/resetting it while the serial device discovery popup is open so you know for sure you're picking the right thing. (Some devices require pressing or holding a button while resetting/powering it up to put it into a "DFU" mode to accept firmware updates first.)

•      Step 6: Click Flash and wait for completion.

•      Step 7 (Companions): After flashing, look for the Bluetooth pin on the display to connect your iOS/Android device. If you don't have a display, your pin will be initialized to 123456. (Make sure to change that soon.) Get logged in via the MeshCore app, set your region to US Recommended, and give your new companion a name.

•      Step 7 (Repeaters): After flashing, click 'Repeater Setup' in the flasher to configure. Set region to 'US Recommended', set name and position.

Q: How do I connect to my MeshCore companion device?

A: You'll need the MeshCore Android/iOS app:

•      Step 1: Download the MeshCore app onto your smartphone/tablet

•      Step 2: Power on your companion device (flashed with BLE Companion firmware).

•      Step 3: Open the app, tap to add a device, and select your companion from the Bluetooth list.

•      Step 4: Enter the pairing PIN if prompted (default is shown in device documentation).

Important: Only BLE Companion firmware supports Bluetooth connection. Repeater firmware cannot be connected via Bluetooth by design - repeaters are configured via USB or remotely over RF.

Q: What settings do I need to configure for the RDU area?

A: Essential configuration:

•      Region/Preset (REQUIRED): Set to 'US Recommended' in the app or flasher. This configures the correct 915 MHz frequency and radio parameters for the United States:
Frequency: 910.525 MHz
Bandwidth: 62.5 kHz
Spreading Factor: 7
Coding Rate: 5
Transmit Power: (depends on your hardware and preferences.)

•      Position (Optional): You can set your GPS coordinates manually in settings. For companions, this is optional. For repeaters, manually setting the position is recommended and appreciated (and can be intentionally inaccurate for security by a couple hundred feet).

•      Send a Flood Routed Advert: After setup, tap the signal/wave icon in the app to broadcast ("Advert") your presence to the mesh. Unlike other systems, MeshCore only discovers nodes when they send adverts - you must manually advertise yourself. Repeaters can, and should, Advert on a schedule automatically.

Patience is Key: Remember, you may not see other contacts immediately. MeshCore only discovers nodes when they send adverts, so it takes time to build your contact list. If you see 'Heard {x} repeat(s)' when sending a message, you're connected to the mesh!

PART 2: Hardware Recommendations

Q: What hardware does RDUMesh recommend for beginners?

A: There is another article that goes into detail here: Recommended Hardware

Q: Where can I buy MeshCore hardware?

A: Check out the Recommended Hardware article for links to stores we tend to like

Q: What's the best transceiver hardware for solar-powered repeaters?

A: Solar repeaters are the backbone of RDUMesh. Prioritize low power consumption:

•      RAK4631 WisBlock: The gold standard. nRF52840 chip is extremely power-efficient. Use with RAK19003 or RAK19007 base board. Add RAKwireless solar panel (5.5 x 3.5 inch panels work great) and large LiPo battery (5000-10000mAh).

•      PeakMesh (seller on Etsy): Fully assembled solar nodes with specs like: RAK4631, 5000mAh battery, dual 1W panels, and weatherproof housing. These can charge even indoors with decent window light and maintain charge through winter in trees. Some of this seller's devices are designed to hang from trees, magnetically stick to poles or the roof of your car, be mounted on walls or fences, etc..

•      Seeed Studio Wio-SX1262 + XIAO nRF52840: Budget option (~$14) for DIY solar builds. Very power-efficient.

•      Much (but not all) of the hardware supported by Meshtastic can also support MeshCore.

Q: Should I use GPS on my repeater?

A: GPS is generally NOT useful on repeaters:

•      Manual Configuration Works Better: Repeater owners typically manually set coordinates in the configuration and leave them alone. This saves power and works perfectly for stationary nodes.

•      Security Consideration: Some operators intentionally provide slightly inaccurate coordinates to make the physical repeater harder to locate, steal, report to authorities, or destroy. Please only "fudge" your location by a couple hundred feet, max. Our signal propagation modelling systems rely on somewhat accurate coordinates.

•      Power Savings: GPS modules consume extra power. For solar nodes with limited panel capacity, skipping GPS extends battery life.

•      When GPS Helps: Mobile companion nodes without smartphones benefit from GPS for position reporting. But for fixed repeaters, manual coordinates are the way to go.

Q: What about the RAK13302 1-watt radio module?

A: The RAK13302 high-power module can transmit at up to 1 watt (30dBm):

•      Power Requirements: Needs 5V internally but has a built-in voltage booster. Can run from standard 3.7V LiPo battery via WisBlock base board.

•      When to Use: Rarely needed in the Piedmont. Better antenna placement and elevation matter far more than transmit power. Save your money. If you want to do it anyway and have money to burn, talk to the back haul strategy team. Otherwise, consider maybe adding a band pass filter to your repeater build.

•      RDUMesh Strategy: We don't need stronger transmitters. We need well-placed high-elevation repeaters with good antennas. A standard RAK4631 mounted at 100+ feet AGL (Above Ground Level) with good horizon views can outperform a 1W radio at ground level practically every time.

•      Legal Limits: A 1W radio paired with the right antenna is right on or even slightly over the legal limits for transmitting on the 915MHz ISM band. Improper use at or beyond this power level might get you in legal trouble. Ask a licensed HAM operator for details.

Q: What firmware should I use for my Heltec V4 repeater?

A: For Heltec V4 repeaters, use the newest firmware (1.13 at the time of this writing) build that includes Pull Request #1398. This PR modifies hardware registers to improve noise floor and SNR, resulting in better reception. Look for recent MeshCore firmware builds that mention PR#1398.

PART 3: Antenna Selection and Configuration

Q: What antenna should I use for a companion node?

A: For mobile companion devices:

•      Stock Stubby Antennas: Work but are the weakest link. Acceptable for testing but upgrade when possible.

•      Quarter-Wave Whip (17cm): Significant improvement, still pocketable.

•      Half-Wave Dipole (37cm): Best performance if you can handle the length. Excellent for wardriving.

•      Omni Pattern Required: Stick with omnidirectional antennas for mobile use to hear nodes in all directions.

•      Antenna dBi?: More dBi (AKA gain) isn't always better. For a companion node, 5dBi is more than enough. 3dBi may even be better since repeaters might be above you and higher gain reduces your signal's ability to reach others above or below you.

Q: What antenna should I use for a repeater?

A: For fixed repeater installations:

•      5-6 dBi Omni (Recommended): The sweet spot. Excellent gain without sacrificing vertical coverage. This is the standard for RDUMesh backbone repeaters.

•      2-3 dBi Omni: Better for lower installations (20-30 feet) where you need maximum vertical spread.

•      8+ dBi High Gain (Not Recommended): Generally avoid in the Piedmont unless you're on a TV tower trying to reach another TV tower 2-3 counties away. High gain focuses the radiation pattern, making it poor at talking to nodes that aren't directly in front of (or in the case of high-dBi omnis, beside) the antenna.

Q: Why not use high-gain antennas (>5.8 dBi)?

A: In the Piedmont, there's limited benefit:

•      Vertical Pattern Compression: Higher gain omni antennas achieve gain by flattening the radiation pattern horizontally while reducing vertical coverage. If you're high up talking to nodes on the ground, this works against you.

•      When High Gain Works: Only for high-to-high long-distance links. Even then, LoRa distance records were set with 5-6 dBi antennas using good elevation and clear line of sight.

•      Height is Might: Better elevation with a modest antenna beats high gain at lower heights almost universally.

Q: Should I use directional antennas?

A: The answer for most people:

Stop making things complicated and just put up more repeaters in great places.

If you have good tall locations, a 5-6 dBi omni will give excellent performance with line of sight in all directions. Directional antennas are rarely worth the complexity in the Piedmont. Find a tall tree on a hill and string up your repeater as high as you can get it.

PART 4: Height is Might - Elevation Strategies

The most important factors in mesh network coverage are elevation and line of sight (LoS). A repeater at 200 feet up on a tower with a basic antenna outperforms a ground-level node with the fanciest antenna money can buy.

Q: Why is height so important?

A: Radio signals travel in straight lines:

•      Line of Sight: At ground level, buildings, trees, and terrain block signals within blocks. At 100+ feet, you have clear line of sight for miles in multiple directions.

•      Fresnel Zone Clearance: Radio signals need clear space around the direct path. Height helps you clear obstacles.

•      Real Example: Users regularly hear the Mount Mitchell repeater from across the region - not because of fancy equipment, but because it's at 6,684 feet elevation.

Q: I have access to tall buildings, trees, towers, or light poles. Can I help?

YES! We'd love to talk to you!

We're actively seeking people with access and permission to high places with skyline views. Contact RDUMesh on Discord if you have access to:

•      Tall buildings (rooftops in Raleigh, Durham, Chapel Hill, Cary)

•      Antenna masts or radio towers

•      High light poles or water towers

•      Very tall trees on hilltops

•      Fire towers, grain silos, or rural factories

A small solar-powered MeshCore repeater is about the size of a large soda can with an antenna. These are self-contained and run autonomously for long periods without maintenance.

Q: Do solar nodes work in trees under canopy?

A: Yes, with the right approach:

•      Pines: Fairly thin canopy. You get clear skies if you dangle a meter or two down from a high limb. Tall, lone pines in hilltops are ideal for tree installations.

•      Deciduous Trees: More challenging. Winter is fine, summer may need oversized panels and batteries. Community members report nodes in oak trees maintaining 72-73% charge through winter.

•      The Trade-off: Height in trees outweighs foliage attenuation. A node 60 feet up in a tree outperforms a rooftop node at 20 feet.

Q: What's the RDUMesh coverage vision?

A: Cover the 16 counties served by RDU airport with a three-tier architecture:

•      Tier 1 - Backbone Repeaters: High-elevation sites (200+ feet, hilltops, towers) with excellent omni antennas covering 10+ mile radius. We may need only 5 to 10 per county.

•      Tier 2 - Distribution Nodes: Rooftop nodes, tree installations at 50-150 feet. Connect to backbone and distribute coverage within neighborhoods.

•      Tier 3 - Last Mile: Lower elevation repeaters. As long as these have line of sight to Tier 2 nodes, they don't need to be above trees.

•      Current Focus: Establishing Tier 1 backbone. Once that's in place, Tier 2 and 3 become much easier.

PART 5: Wardriving and Network Discovery

Q: What is wardriving for MeshCore?

A: Wardriving is driving around with a MeshCore companion device to discover and map repeaters and coverage. You can identify coverage gaps, test signal strength, and gather data to improve the network - all while the data gets uploaded to mapping services when you have internet connectivity.

Q: How do I start wardriving?

A: Here's how:

•      Get MeshMapper: Sign up for the MeshMapper app (currently in TestFlight for iOS). Ask in the RDUMesh Discord for an invitation link.

•      Use a Decent Antenna: External omni antenna recommended - dipole or whip between 17cm and 34cm (quarter-wave to half-wave) significantly improves reception over stock stubby antennas or antennas inside your vehicle.

•      Enable GPS: Make sure your companion device has GPS enabled so MeshMapper can plot where you discovered each repeater.

•      Drive and Log: Drive around with your companion powered on, MeshMapper app running, and actively pinging. It automatically logs all repeaters you hear.

•      Having Trouble?: Chat with us in Discord and someone will be able to help you out.

Q: What should my noise floor be when wardriving?

A: Noise floor depends on environment and hardware:

•      Ideal Quiet Environment: Around -110 dB or lower indicates minimal interference.

•      Heltec V4: The Low Noise Amplifier may inject noise, so around -95 dB is typical. Newer firmware with PR#1398 may help improve this.

•      Context Matters: Urban areas have higher noise floors than rural areas.

Q: I found a repeater that shows up gray/offline in MeshMapper. What do I do?

A: Help grow the network:

•      Step 1: Return to that area and get within range.

•      Step 2: Use your MeshCore app to discover the repeater and see it in your contact list.

•      Step 3: Send the owner a friendly message on their public channel inviting them to join RDUMesh and Discord.

•      Why: Many people set up repeaters but don't know about local communities. Your outreach connects isolated nodes to the larger network.

PART 6: How to Help the Community

Q: I have a location with power and data. Would that help?

A:

We stick with solar and off the internet. Here's why:

•      Off-Grid Resilience (THE Key Reason): RDUMesh is designed to work when the internet and power grid fail. Grid power fails during hurricanes, ice storms, and emergencies - exactly when we need the mesh most. Solar nodes keep working when everything else is down.

•      Cost: Solar hardware can be cheaper and require zero ongoing electricity costs.

•      Simplicity: Self-contained solar nodes don't require running cables or dealing with electrical codes.

Our Philosophy: We do NOT want the internet used to interconnect nodes that couldn't otherwise connect via RF. If we have connectivity problems, we solve them with better repeater placement and RF solutions - not internet backhaul.

Q: Can I monitor the mesh and send data to the internet?

A: Yes! This is different from using the internet for routing:

•      Observer Nodes Are Welcome: You can set up observer nodes that listen to the mesh and report data to services like MeshRank, LetsMesh.net, or MeshMapper. These help with wardriving, network analytics, and understanding coverage.

•      What Observers Do: Observer nodes listen silently and upload what they hear to internet services for mapping and analysis. They don't participate in routing - they just observe.

•      The Key Distinction: Monitoring/reporting is fine. Using the internet to route mesh messages is not aligned with RDUMesh goals. The mesh must work WITHOUT the internet.

Q: What's the best way to help if I'm not technical?

A: You don't need technical skills to make huge impact:

•      Access to Locations: Know people with tall buildings, property owners, or connections to organizations with towers/rooftops? That's incredibly valuable. You can connect RDUMesh members to prime installation sites.

•      Community Building: Spread the word. Talk to neighbors, local emergency preparedness groups, and community organizations.

•      Run a Node: Even just keeping a node powered on at your house contributes. Every companion helps, every repeater is critical.

•      Wardriving: Drive around discovering repeaters and helping isolated operators connect to the community.

PART 7: Privacy and Anonymity - The Reality

Q: Just how anonymous is MeshCore?

A: Let's be realistic about anonymity:

•      You're Transmitting on RF: You're broadcasting on a radio frequency with a transmitter. The fact that you're transmitting and that your transmitter has a unique identity (public key) significantly limits TRUE anonymity.

•      Message Traces Exist: Messages may traverse multiple repeaters to reach their destination. Each hop creates a trace showing the path your message took through the network. Those repeaters have known locations.

•      Observer Nodes: Some nodes are configured as observers that report information about the mesh, telemetry, traces, and messages to the public internet (services like MeshRank, LetsMesh.net). These help with mapping and analytics but reduce anonymity.

•      Encryption Varies: Peer-to-peer direct messages use encryption. However, messages posted to public chat rooms are in clear text to anyone within range of that room and its repeaters.

•      Physical Location: If you have a stationary repeater or companion, people can triangulate your general location by signal strength and message timing.

Bottom Line: MeshCore provides operational privacy for everyday communications and keeps your messages secure from casual observation. But it's not designed for high-threat anonymity scenarios. Understand what you're getting.

Q: Can I be completely anonymous on MeshCore?

A: You can be more or less private, but not truly anonymous:

•      Generic Node Names: Use non-identifying names. But your public key is still unique to your device.

•      Disable/Obscure Location: Don't broadcast GPS. Manually set slightly inaccurate coordinates (or none at all) for repeaters if desired.

•      Use Encrypted Channels: Direct messages are encrypted, but avoid public chat rooms for sensitive information.

•      Mobile Nodes Help: Constantly changing locations makes you harder to locate than stationary nodes.

•      Realistic Expectations: In a small community, your communication patterns and writing style may identify you despite technical anonymity measures.

Q: Why aren't community events recorded?

A: RDUMesh takes privacy seriously. Events like workshops deliberately turn off recordings, transcripts, and logging to:

•      Encourage Participation: People feel comfortable asking questions and sharing setups without worrying about being recorded or quoted.

•      Privacy First: Many people are interested in mesh networking specifically for privacy. Recording would contradict community values.

•      Documentation Alternative: We create FAQs like this that capture knowledge without compromising anyone's privacy.

PART 8: Advanced Topics and Network Strategy

Q: Should I experiment with different LoRa settings?

A: Stick with the recommended settings:

•      Use 'US Recommended': The default US preset works well. Don't change LoRa parameters unless you have a very specific reason and understand the implications.

•      Compatibility Matters: Veering from defaults in incompatible ways makes your nodes useless to the wider mesh.

•      The Real Solution: We don't need modified LoRa settings. We need well-distributed, well-placed high-elevation repeaters.

Q: What about complex linking schemes with wires or directional bridges?

A: The short answer:

Stop making things complicated. Put up more repeaters in better places.

Simplicity wins. If you have good tall locations, a 5-6 dBi omni gives excellent performance with line of sight in all directions. Complex schemes are rarely worth it in the Piedmont.

Q: How does MeshCore routing actually work?

A: MeshCore uses hybrid flood-then-direct routing:

•      Initial Flood: First message to a destination floods across repeaters to discover a path.

•      Path Learning: When the destination responds, the path is remembered.

•      Direct Routing: Subsequent messages use the known path directly, saving bandwidth.

•      Automatic Fallback: If the path breaks, the system automatically falls back to flooding to re-discover a new route.

This is much more efficient than systems that flood every message.

Q: What's the difference between public channels and private messages?

A: Understand the security implications:

•      Public Channels/Rooms: Messages broadcast in clear text. Anyone within range of the room and its repeaters can read them. Think of it like an unencrypted radio channel.

•      Direct Messages (Peer-to-Peer): Encrypted communications between two specific nodes. Content is protected, though metadata (who's talking to whom, when) is still visible.

•      Room Servers: Store-and-forward servers that hold messages for offline users. Useful for asynchronous communication.

Q: Should I experiment with MeshCore?

A: Yes, but responsibly:

•      Innovation Welcome: This is a community network. Try things! Innovation comes from experimentation.

•      Maintain Compatibility: Stick with US Recommended settings so your nodes remain discoverable and available to the greater mesh.

•      Don't Disrupt: Avoid configurations that flood channels with excessive traffic.

•      Share Results: If you try something interesting, share findings on Discord. Community learns from both successes and failures.

Additional Resources

Official MeshCore Resources:

•      MeshCore Official Site: https://meshcore.io

•      MeshCore Web Flasher: https://flasher.meshcore.io

•      MeshCore GitHub: https://github.com/meshcore-dev/MeshCore

•      MeshCore Discord: Join via meshcore.io

North Carolina Resources:

•      RDUMesh Discord

Mapping and Analytics:

•      MeshCore Map: https://map.meshcore.io

•      MeshRank: https://meshrank.net

•      LetsMesh Analyzer: https://analyzer.letsmesh.net

•      MeshMapper (iOS)

Hardware Suppliers:

•      store.rokland.com - RakWireless/WisBlock, Lilygo, Heltec equipment

•      PeakMesh on Etsy - Turnkey solar-powered repeaters

•      Seeed Studio - T1000-E and LoRa devices

•      Amazon - Heltec, LILYGO T-Deck, general components

Community Comparisons:

•      Austin Mesh MeshCore vs Meshtastic: https://www.austinmesh.org/learn/meshcore-vs-meshtastic/

Welcome to RDUMesh!

We're building something resilient here in Central North Carolina - a community-owned communications network that works when everything else fails. MeshCore's planned infrastructure approach with dedicated repeaters lets us build reliable, scalable coverage across the 16 counties served by RDU airport.

Remember: Height is might and solar is resilience. Keep your repeaters high and your messages flowing. This mesh is built to last.

See you on the mesh!

- The RDUMesh Community

Last Updated: February 2026

*(1) New versions of MeshCore allow a companion to repeat messages but this is handled on a different frequency (918 vs 910MHz), effectively isolating those companions in repeat-mode from the rest of the MeshCore infrastructure and Companions that aren't repeating.

When you first join the RDUMesh, you're faced with a single channel: Public.

The Public channel is like the public square. Anyone and everyone who's on the mesh starts there by default. If you're a gamer, you might consider it the spawn point of the mesh.

But is there more?

Yes. And... not yet.

Yes.

Here are a few channels to explore on the RDUMesh that already exist right now:

• #test - This is the best place to test to see if the mesh is working. There are usually helpful people listening who will respond (but maybe not right away) to let you know they caught your test message. This helps a lot to keep Public free of "can anyone hear me?" type posts.
• #rdumesh to talk about the mesh itself!
• #2600 - Hacker culture lives here.
• #apex
• #bullcity and #durham - Which one will win? Or maybe there's a place for both? Tell us what you think.
• #cary
• #emergency - This is a good one to have and a good one to listen to. But please don't test there, don't post anything unless there's a real emergency and your primary means of communication aren't working.
• #hamradio is a great one to have if you're a licensed radio amateur (or ham-curious). This convention is being followed by meshes in other cities, as well. So being a member of it here, your mesh radio will still accept #hamradio chat in other areas when you travel with your MeshCore Companion device.
• #raleigh

Not yet.

Anybody can create new channels on the mesh.

Anyone.

If you're meeting people on the mesh and you share a common interest, consider creating a lasting place to gather with your new friends by starting a new hashtag channel. And let us know about it on Discord so we can add it to the list!

Keeping hardware, especially repeaters, up to date can be challenger. Nodes on roofs or placed out of reach without ladder/pole access. Luckily for us, NRF52 based hardware supports over the air (OTA) upgrades over bluetooth. This means you can use your Android or iOS device to update firmware. I've read iOS can be bit more problematic for this though I can't confirm this.

But first let's talk about bootloaders. These devices actually have multiple firmware components and typically we are just updating the application that is started by the bootloader. The bootloader itself handles allowing updates via serial, usb drag and drop (UF2), and via bluetooth. The problem we might run in to is that bluetooth can be the flakiest of process. A bad flash might leave the device unable to boot. You could still flash via serial or UF2 to recover, but this leaves you having to retrieve the device. We can get around this by using a modified bootloader that defaults to accepting bluetooth upgrades if it can't boot the application. Failed upgrades allow us to try again, while still allowing serial or UF2 upgrades if needed. A modified bootloader is available here. You can see boards supported here. I've personally had success with T1000-E and Rak 4631 hardware.

Follow the instructions there for details but the TLDR version is:
1. Download the right UF2 file from the releases
2. Enter DFU mode then drag and drop the UF2 file to the device.

After this, updating repeater (or even room firmware) will go like this:
1. Install the appropriate DFU update app (for Android, for iOS)
2. Download the right firmware ZIP file for your device/role here.
3. Be physically very near to the device (as Bluetooth range is limited). In Meshcore, sign in to manage the device, then go to "Command Line" and enter the command start ota. You should get confirmation back with bluetooth MAC address.
4. Open the DFU update app and make sure your settings match the recommendations here.
5. Select the right Meshcore firmware ZIP file, select the right device (should be something like RAK4631_OTA and have the same MAC from last step), and hit the Upload button.
6. If anything fails, you should be able to simply try again. I sometimes have to try a second time. If the device isn't available anymore in the bluetooth device list, it may have booted up in old firmware version and require you to go step 3.

If anything goes completely sideways, reach out on Discord and hopefully we can figure it out!

Companion nodes are nodes that send and receive messages and are how people interact with each other over the mesh. If you're looking for your first node, a companion is what you'll want to start with.

Cards & Clips

Card nodes are a great option for getting started. They're very easy to carry around in a pocket or attach to a bag, and typically have some form of water resistance so they're great for outdoor use. Since they don't have a display, you'll need to pair with a phone to send/receive messages with these.

SenseCAP Card Tracker T1000-E for Meshtastic

It is a high-performance tracker designed for Meshtastic, as small as a credit card, effortlessly fitting in your pocket or attaching to your assets. It embeds Semtech’s LR1110 (Supports 863-928 MHz range), Nordic’s nRF52840, and Mediatek’s AG3335 GPS module, providing Meshtastic users with a high-precision, low-power positioning and communication solution.

SenseCAP Card Tracker T1000-E

WisMesh Tag from RAKwireless & MOKOSmart - Meshtastic compatible card

What is WisMesh Tag? The WisMesh Tag is your compact companion for location tracking and mesh messaging. Built for Meshtastic users who want something portable, reliable, and ready-to-go. Unlike DIY builds or limited designs like the T1000E, the WisMesh Tag delivers reliable outdoor performance with a 1000mAh battery,

RoklandRAKWireless

Handheld

These nodes are bulkier than the cards above, but you gain the ability to use an external antenna as well as a display for checking the node's status and reading messages without needing to have a phone paired.

This class of device is also where you'll see more microcontroller options. We recommend looking for nRF52-based nodes, since they're significantly more power-efficient than ESP32-based ones.

Some pre-assembled nRF-based options:

H2T - Complete Device: Heltec T114 with GPS running Meshtastic®

THIS IS IN PRE-ORDER [Restock late-February] A GPS enabled Meshtastic® device powered by the Heltec T114 V2 board. Unique 3D printed design, now in ASA for ultimate UV and heat resistance. Using the power efficient nRF52840 chipset, the H2T will last over 2 days with GPS enabled. Stay connected to the Meshtastic® app o

muzi ᴡᴏʀᴋꜱmuzi ᴡᴏʀᴋꜱ

Elecrow ThinkNode M1 LoRa Meshtastic radio + 1.54″ EPD Screen GPS nRF5

ThinkNode M1 Meshtastic Device – Stay Connected Without Internet Prices may be higher than manufacturer’s website as tariffs are included The Elecrow ThinkNode M1 is a compact, high-performance Meshtastic device designed for outdoor adventures, emergency communications, and environmental monitoring. With powerful LoRa

RoklandElecrow

You can also buy a bare Heltec T114 and bring your own case, battery, and antenna if you prefer to DIY:

Heltec Mesh Node T114 with optional 1.14 inch TFT display (v2 version

Heltec T114 v2, updated December 2024.Mesh Node T114 is a Low Power Consumption development board based on nRF52840 and SX1262, supports LoRa and Bluetooth 5.0 with integrated various power interfaces (5V USB, lithium battery and solar panel) optional 1.14 inch TFT display, and has powerful long-distance communication

RoklandHeltec

The Heltec V3 is another popular and cost-effective option that can be bought as a kit or just the bare board, but note that its battery life will be worse due to it being ESP-32 based. For battery-powered nodes that you carry with you, we advise picking something nRF-based instead, despite the popularity of the V3.

Standalone

Standalone nodes include a keyboard and larger display, which allows sending and receiving messages without carrying a phone. These nodes are the most expensive, but also the most full-featured. Firmware such as Ripple or MeshOS are most frequently used on these to best take advantage of the extra power and features.

LILYGO® T-Deck Portable Microcontroller Programmer LoRa 915 MHz

T-Deck is a pocket-sized gadget with a 2.8-inch, 320 x 240 pixel IPS LCD display, a mini keyboard, and an ESP32 dual-core processor. It is not a smartphone, though it looks like one- but you can use your programming knowledge to turn it into a standalone messaging device, or use with coding software for programming. Ro

RoklandLILYGO

LILYGO® T-Lora Pager US 915 Mhz LoRa + ESP32-S3 Handheld AIOT Programm

Why is pricing higher than LILYGO site? For USA there are 27.5% import tariffs that are already included in the price. This item also ships free within the USA. The price you see on our site is your total price, with sales tax collected in some states.T-Lora Pager is the new member of the LILYGO T series, the compact e

RoklandLILYGO

Antennas

For nodes with an external antenna connector, the stock "stubby" antenna that comes with many nodes can be a limiting factor for range. If you'd like to improve your RF performance, upgrading to a better antenna is a way to do that (though there are many other factors at play - bad terrain and repeater proximity can still cancel out any improvement you might see from a better antenna.)

The Muzi Works whip antenna is the most commonly recommended upgrade:

Whip Antenna – 17cm

Upgrade your antenna to this flexible whip design. Improves performance, measured SWR of 1.3 compared with the stock stubby antenna at an SWR of 3.5. SWR is a measure of transmission efficiency, how much power from the LoRa radio makes it out into the world via the antenna. SWR 1.3 = 98% efficient SWR 3.5 = 69% efficie

muzi ᴡᴏʀᴋꜱmuzi ᴡᴏʀᴋꜱ

There's many other antenna vendors out there, but be wary of no-name or counterfeit sellers - advertised specifications are not always correct.

Repeaters

Repeaters are responsible for routing traffic across the mesh, and define the "backbone" of the network. To reach someone else on the mesh, there needs to be a path of repeaters between your companion node and theirs for the message to pass through. Most repeaters are solar powered to ensure that the mesh remains intact even if grid power fails.

Adding repeaters in strategic locations is key to improving coverage of the mesh, both on towers and tall structures for regional coverage, as well as roofs, attics, and balconies for stronger neighborhood-level coverage.

Pre-built

PeakMesh Magnet Mover - Solar node for roofs and horizontal surfaces

PeakMesh Magnet Climber - Solar node for poles and vertical surfaces

PeakMesh Altitude - Hanging solar node for trees

SenseCAP Solar Node P1-Pro for Meshtastic

It is a solar-powered communication node that integrates the XIAO nRF52840 Plus main controller, the Wio-SX1262 LoRa module, and the XIAO L76K GPS module. It is specifically designed for areas without network coverage. With a built-in battery, it supports long-distance communication, precise positioning, and low-power operation. It’s suitable for expanding network coverage in outdoor areas. Power your projects together! Enjoy an automatic 10% off when you purchase any two or more devices from the Wio Tracker L1 series (SKUs: 114993648, 114993649, 114993653, 114993654) and the Solar Node series (SKUs: 114993633, 114993643). Offer valid from January 27.

DIY

If you have the tools and know-how, building a repeater from parts is also possible, and in some cases may be more cost-effective than buying something pre-built. There are plenty of guides to building this type of node online.

For most repeaters, we recommend the RAK WisBlock series of boards:

RAKwireless WisBlock Meshtastic Starter Kit US915 SKU 116016

Meshtastic® is an off-grid messaging system using inexpensive hardware to create your personal mesh. Radios forward messages to the next node to distribute them over the network. Communicate kilometers/miles between nodes. Internet-connected relay nodes enable the conversation to move online too.RAKwireless WisBlock Me

RoklandRAKWireless

You'll also want a waterproof enclosure, batteries, solar panel(s), and antenna. Also consider how to get power connections into the enclosure - cable glands of an appropriate diameter are typically used for this.

Antennas

A frequent recommendation for repeaters is this ALFA model (beware of counterfeits):

ALFA AOA-915-5ACM 5 dbi Omni Outdoor 915MHz 802.11ah Mini LoRa Antenna

ALFA Network AOA-915-5ACM is the original dipole small form factor antenna for the People’s Network (Helium) and IoT. Are you an ISP or installer looking to print your company’s name on the antenna, contact us for bulk/OEM order options.This antenna is compatible with Meshtastic devices (requires N-female connector),

RoklandRokland

Larger outdoor antennas typically use an N-type connector, so you may also need to purchase a pigtail/adapter to connect the antenna to the SMA or U.FL connector on your node. Pre-built nodes usually include this.

MeshCore is a text messaging system that runs on small radio devices—no internet, no cell service, no monthly fees. Your messages hop from radio to radio across the 16-county Triangle region (eventually), encrypted and private.

Solar-powered relay stations on rooftops, homes, businesses, community buildings, and hilltops pass your messages across the area. When storms knock out power and cell towers fail, the mesh keeps working. Because radio signals travel through the air—they can't be cut by fallen trees or washed away by flooding.

What you get:

• Free to use—no subscriptions, no contracts
• Private messages encrypted with AES-256 (same standard banks use)
• Access to neighborhood bulletin boards (Room Servers) for community updates
• A backup communication system that works when everything else fails

What it costs:

• Radios: $40-100+ depending on features
• App: Free
• Monthly fees: Zero

The network belongs to the people who build it.

Room Servers act as neighborhood bulletin boards. Anyone on the mesh can post and read messages—great for sharing local updates, event info, or (during emergencies) road closures and resource availability.

Getting started

Phone-connected devices

Best if you want to message from your phone using a small companion radio:

RAK Wismesh Tag - Compact, battery-efficient
Buy on Rokland | ~$50

Seeed Studio SenseCAP T1000-E - GPS tracking, long battery life
Buy from Seeed | ~$40-50

These connect to your phone via Bluetooth. The free MeshCore app handles all messaging.

Standalone devices

No phone needed—built-in keyboard and screen:

Lilygo T-Deck Plus - Full keyboard, works completely independently
Buy on Rokland | ~$100

Lilygo T-LoRa Pager - Compact pager-style device
Available from Lilygo | ~$115

Perfect for off-grid communication or keeping as a backup when your phone dies.

These work entirely without a phone, but go into this eyes-open that the hardware does really affect your user experience so there might be more of a learning curve to using it!

Set up your device

1. Get your hardware - Order from the links above
2. Flash MeshCore firmware - Go to flasher.meshcore.io, connect your device, select your model, and click flash (takes 2 minutes)
3. Download the app (if using phone-connected device):
   • Android: Search "MeshCore" on Google Play
   • iOS: Search "MeshCore" on Apple App Store
4. Configure frequency - Set to "US/Canada Recommended" (910.525 MHz)
5. Announce yourself - Send a flood advert to let the network know you're here
6. Post a message - Send a message in the Public channel saying hi to everyone.

Need help? Full setup guides at meshcore.io

Join the community

Questions? Want to say hi? Our Discord is the place to ask for help, share tips, or find out about local mesh events.

• Join RDUMesh on Discord
• Join Triangle Mutual Aid - Comms on Discord

Why join?

When Hurricane Helene hit in 2024, communities across NC lost power and cell service for days. People couldn't coordinate rescues, share warnings, or check on neighbors.

Traditional infrastructure runs through cables in the ground. Storms destroy it. Radio signals travel through the air. As long as a relay has solar power, it keeps working.

But the mesh isn't just for disasters.

Ever tried to text someone at a packed concert, the State Fair, or Hopscotch? Cell networks get overwhelmed when thousands of people crowd into the same area. The mesh keeps working.

Use it to stay connected with friends at crowded events, coordinate with your hiking group in areas with spotty coverage, or chat with neighbors. The more people use it during normal times, the more prepared everyone is when it really matters.

This is community infrastructure. It serves everyone—especially the people who have the fewest backup options when regular communications fail.

Resources

• Main website: meshcore.io
• Firmware flasher: flasher.meshcore.io
• Network map: meshcore.io/map.html
• Android app: Google Play Store (search "MeshCore")
• iOS app: Apple App Store (search "MeshCore")

RDUMesh is a 501(c)(3) nonprofit building community-owned communications infrastructure across the 16-county Triangle region. When the grid fails, you can still reach your neighbors.

If you're here, you may have heard something about Meshtastic or MeshCore, or more generically about off-grid radio mesh communications. And you might be wondering how to get started on it if you're in the Raleigh-Durham-Chapel Hill area.

When I got started with mesh a few years back, there weren't many other people out there using it. At least not enough of us to establish a viable mesh network. And when we did get together in numbers, sometimes those mesh networks would crash and burn spectacularly under the load.

As the movement grew we learned a few things along the way. Not the least of which:

1. Infrastructure matters. Having one or more well-placed repeater sites can drastically improve the mesh experience for many people.
2. Coordination matters. If everyone is off using their own settings, not talking to their neighbors about how they want their radios to work together, things never really get off the ground.
3. Humans matter most. Early mesh efforts got too carried away with the technical capabilities, sharing sensor telemetry and GPS position details back and forth in the background. But as meshes grow, there's precious little radio bandwidth left to reliably pass messages from person to person.

RDUMesh is taking an opinionated approach to providing mesh services in the Triangle.

• We will build out core infrastructure that helps community members to reliably connect over radio to one another, and across communities in the region.
• We will coordinate with other local community groups to make sure we are helping and not hurting their communication needs. We will also coordinate with mesh groups beyond the Triangle to make sure that as their meshes mature, we can peacefully co-exist.
• We will put front and center the needs of real people and the communities they live in and serve. This is all for nothing if we aren't helping people to reliably connect with their neighbors.

Things are just getting started. The web site is brand new today (January 18, 2026). The 501(c)(3) paperwork is still underway.

But we're already working side by side with Triangle Mutual Aid. TMA is already mobilizing in parallel around the critical need for off-grid communications infrastructure, and we see a tremendous opportunity to work closely with them as a first class example of why RDUMesh is needed.