Home The Playbook Directory
Learn
Settings Guide Field Guides & Resources Certifications
Get
Meshtastic Meshcore Reticulum Nodes About Contact
Open Stack, Open Build

Node Star
Mesh Gateway

v0.1  ·  Node Star  ·  Open by Default

We are building a device that connects to every major mesh network at once. Meshtastic. MeshCore. Reticulum. One box. Always on. No configuration required.

Node Star Mesh Gateway — Concept Render
Concept Render — Node Star Mesh Gateway
01

What We Are Building

Right now the mesh networking world is fragmented. Meshtastic, MeshCore, and Reticulum are three separate communities using three incompatible protocol stacks. If you want to participate in all three, you need three separate devices. Nobody has built the thing that bridges them.

That is what the Node Star Mesh Gateway is. A compact appliance — roughly the size and footprint of a home Wi-Fi router — with three dedicated LoRa radios inside, each running its own protocol firmware. It sits on your shelf, plugged into power and Ethernet, and it participates in all three mesh networks simultaneously, around the clock.

You manage it from a browser on your local network. No terminal required. No SSH. You plug it in and it works.

One-Line Version

A home router for mesh networks. Always on, three radios, three communities, one box.

02

Why We Are Doing This

Running a permanent mesh node is harder than it should be. Even for technically capable people, keeping a Raspberry Pi stable, managing USB device persistence, writing systemd services, and handling firmware updates across multiple radios is a real time investment. Most people give up before they have something reliable.

We want a fixed node that just runs. The kind of thing you forget about because it works. The mesh equivalent of your cable modem — anonymous, unglamorous, and always there.

And we want it to speak every dialect. The fragmentation between Meshtastic, MeshCore, and Reticulum is a problem for the whole community. A device that participates in all three creates a bridge between groups of people who currently cannot hear each other.

03

How It Works

Three Heltec LoRa32 V3 modules connect to a Raspberry Pi 5 via a powered USB hub. Each module runs independent firmware for its target protocol. The Pi runs all three network daemons simultaneously and will eventually bridge traffic between them where possible.

LayerComponentProtocolNotes
BrainRaspberry Pi 5 (4GB)Runs all services, web UI, bridging logic
Radio 1Heltec LoRa32 V3MeshtasticMeshtastic firmware, 915 MHz
Radio 2Heltec LoRa32 V3MeshCoreMeshCore firmware, 915 MHz
Radio 3Heltec LoRa32 V3ReticulumRNode firmware, 915 MHz
HubPowered USB hub (4-port)Powers and connects all three radios
PowerUPS HAT or inline UPSBattery backup, clean shutdown
UplinkEthernet + onboard Wi-FiTCP/IPInternet bridge for Reticulum testnet
Antennas915 MHz whip x3LoRa RFExternal SMA ports on enclosure
Node Star Mesh Gateway — Design Blueprint
Design Blueprint — NS-01-A (Concept)

All three radios operate on 915 MHz. Physical separation inside the enclosure and staggered channel assignments minimize interference between simultaneous transmitters. Each radio connects to its own external antenna via U.FL to SMA pigtail, with three SMA ports on the enclosure face. You can upgrade to high-gain antennas without opening the device.

04

Where We Are Now

We are at the start. Hardware is being sourced. The architecture is settled. The software approach is clear. What we do not have yet is a working prototype on a desk with all three radios talking simultaneously — and that is the next thing that needs to happen.

Here is the honest roadmap:

Phase 01 Working Prototype

Get all three radios running simultaneously on one Pi. Desktop assembly, no enclosure. Prove the architecture works before committing to anything else.

  • Source Pi 5, three Heltec LoRa32 V3 units, powered USB hub, antennas, pigtails
  • Flash Meshtastic, MeshCore, and RNode firmware to each respective radio
  • Configure rnsd, confirm Reticulum connectivity
  • Verify all three radios run simultaneously without USB enumeration conflicts
  • Document everything as we go
We Will Know It Worked When A message from a Meshtastic app, a MeshCore client, and a Sideband client are all received and logged by the same box.
Phase 02 Software Hardening

Make it reliable enough to run unattended for weeks. Add a web UI. Start bridging where we can.

  • systemd services for all three protocol daemons with watchdog timers
  • udev rules for consistent USB device paths across reboots
  • Web UI: per-radio status, uptime, message counters
  • Reticulum to Meshtastic bridge (evaluating the acehoss bridge project)
  • 7-day continuous operation benchmark
We Will Know It Worked When The device runs for 7 days without anyone touching it, and at least one cross-protocol message relays successfully.
Phase 03 Product Design

Turn the working prototype into something that looks and ships like a product. Enclosure, fit and finish, setup experience.

  • Evaluate CM4 vs Pi 5 for production (CM4 preferred for compact form factor)
  • Enclosure with three external SMA ports, Ethernet, USB-C power
  • Battery backup for clean shutdown on power loss
  • First-run setup wizard — zero configuration out of box
  • Thermal testing under sustained load
We Will Know It Worked When A beta tester plugs it in and joins all three networks within 10 minutes without reading a manual.
Phase 04 Launch

Ship a limited first run to the community that helped build it.

  • 25 to 50 units, assembled and tested
  • Pre-order or direct purchase through the Node Star store
  • Gather feedback, ship v1.1
05

What We Do Not Know Yet

We are being honest with you about the open questions. If you have worked through any of these, we want to hear from you.

How Deep Does the Bridging Go?

Getting all three radios running simultaneously is straightforward. Full bidirectional message relay between Meshtastic, MeshCore, and Reticulum is a much harder problem. We will start with a dashboard that shows traffic across all three networks and work toward bridging from there. How far we get depends partly on what already exists in the ecosystem.

DIY Kit or Pre-Assembled?

We suspect the community wants both. A documented parts list for people who want to build their own, and a pre-assembled unit for people who just want it to work. We will offer whatever we can support at the volumes we can reach.

FCC and Regulatory Questions

LoRa on 915 MHz is license-free under FCC Part 15. Selling a product commercially with integrated radios may require additional certification. We are using pre-certified modules which simplifies this, but we need legal review before a commercial launch.

What Are We Missing?

Genuinely asking. If you have built something similar, hit a wall we have not thought about yet, or know of existing work that overlaps with this — tell us.

06

Open by Default

Open protocols. Open firmware. Open hardware. The entire stack this device runs on was built by people who shared their work. Building the Mesh Gateway in public is the only approach that makes sense given what it is and who it is for.

This community has knowledge we do not have. People who have already wrestled with USB persistence on Pi, systemd watchdog configs for serial devices, the current state of the Reticulum-Meshtastic bridge. Publishing the architecture and the problems openly is how that knowledge finds its way into the build.

Get Involved

Follow the build and join the conversation on Mastodon: https://mastodon.social/@nodestar. If you have relevant experience with any part of this stack, like Reticulum, MeshCore, Meshtastic serial interfaces, Pi hardware, or enclosure fabrication, reach out.

This is a community project being built by a small team. Your input changes what gets built.

07

The Phase 1 Parts List

For anyone who wants to build along with us. This is what we are sourcing right now.

ComponentPurposeQtyEst. Cost
Raspberry Pi 5 (4GB)Main SBC1$60
Pi 5 Official Power SupplyStable 27W USB-C power1$12
Heltec LoRa32 V3Meshtastic radio1$20
Heltec LoRa32 V3MeshCore radio1$20
Heltec LoRa32 V3Reticulum / RNode radio1$20
Powered USB Hub (4-port)Connect all radios to Pi1$15
915 MHz Whip AntennasLoRa RF3$24
U.FL to SMA PigtailsHeltec to external antenna3$15
MicroSD Card (32GB)OS and storage1$10
Total~$196