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.
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.
A home router for mesh networks. Always on, three radios, three communities, one box.
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.
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.
| Layer | Component | Protocol | Notes |
|---|---|---|---|
| Brain | Raspberry Pi 5 (4GB) | — | Runs all services, web UI, bridging logic |
| Radio 1 | Heltec LoRa32 V3 | Meshtastic | Meshtastic firmware, 915 MHz |
| Radio 2 | Heltec LoRa32 V3 | MeshCore | MeshCore firmware, 915 MHz |
| Radio 3 | Heltec LoRa32 V3 | Reticulum | RNode firmware, 915 MHz |
| Hub | Powered USB hub (4-port) | — | Powers and connects all three radios |
| Power | UPS HAT or inline UPS | — | Battery backup, clean shutdown |
| Uplink | Ethernet + onboard Wi-Fi | TCP/IP | Internet bridge for Reticulum testnet |
| Antennas | 915 MHz whip x3 | LoRa RF | External SMA ports on enclosure |
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.
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:
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
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
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
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
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.
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.
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.
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.
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.
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.
The Phase 1 Parts List
For anyone who wants to build along with us. This is what we are sourcing right now.
| Component | Purpose | Qty | Est. Cost |
|---|---|---|---|
| Raspberry Pi 5 (4GB) | Main SBC | 1 | $60 |
| Pi 5 Official Power Supply | Stable 27W USB-C power | 1 | $12 |
| Heltec LoRa32 V3 | Meshtastic radio | 1 | $20 |
| Heltec LoRa32 V3 | MeshCore radio | 1 | $20 |
| Heltec LoRa32 V3 | Reticulum / RNode radio | 1 | $20 |
| Powered USB Hub (4-port) | Connect all radios to Pi | 1 | $15 |
| 915 MHz Whip Antennas | LoRa RF | 3 | $24 |
| U.FL to SMA Pigtails | Heltec to external antenna | 3 | $15 |
| MicroSD Card (32GB) | OS and storage | 1 | $10 |
| Total | ~$196 | ||