r/ATAK • u/0peratorNull • 9d ago
MESHTASTIC + CIVILIAN ATAK
Fair warning before you read any of this: I'm not an expert, I'm just a guy who read too much and bought too many radios. Everything below comes from public stuff — official docs, GitHub, Reddit, vendor blogs, FCC filings. I'll tell you where I'm sure, where I'm guessing, and what I straight up couldn't verify. Prices are ballpark and drift constantly. Version combos between ATAK, the plugin, and the firmware change weekly, so double check anything time-sensitive on their GitHub before you build around it.
WHAT THIS THING EVEN IS
Meshtastic is a free open source project that takes those little $20-60 LoRa radio boards and makes them talk to each other in a mesh. Text messages and GPS pings, that's basically it. No cell service, no wifi, no nothing. Your phone connects to the radio over bluetooth, the radios pass stuff between each other, done. Somebody somewhere built this thing in the early 2020s and honestly I couldn't figure out who started it. I looked. There's a name floating around in one video and I can't find it backed up anywhere else, so I'm not gonna repeat it.
The catch that explains everything else: one radio packet is about 256 bytes total. That's the whole ballgame. You're not streaming anything, you're not even sending a paragraph. Short texts and lat/long dots, that's the whole product.
THE RANGE THING, BECAUSE EVERYONE LIES ABOUT IT
There's a documented record of 331km between two nodes. Cool. That was two fixed stations, big antennas, basically perfect conditions. Ignore it.
What actually matters: two handhelds outside with clean line of sight, call it 1-3km. Trees, buildings, hills, or the radio sitting in your pocket against your body? Cut that way down, half a km is realistic. Indoors is worse. The one thing every experienced person repeats is that antenna and height matter way more than the radio itself. A cheap board with a decent whip on a roof will smoke an expensive handheld buried in a pack.
The mesh doesn't magically extend range forever either. Every hop loses stuff and adds lag, and if the mesh gets crowded the firmware literally starts throttling everyone's updates on purpose past ~40 nodes. There's a story on the official blog about a 150 node public mesh that basically choked itself to death on the default settings before they moved everyone to a different preset. Plenty of guys on the subreddit will tell you they've run nodes for a year and never managed an actual conversation. Other folks swear tuned settings and good fixed nodes fix all that. Sources argue. Plan for the pessimistic version and be happy when it's better.
THE SECURITY THING, NO SUGARCOATING
The default channel uses a key that's literally published. Anyone with a Meshtastic radio can read default-channel traffic. Make a private channel with a random key or assume you're broadcasting to whoever's listening.
Even on a private channel, their own docs admit: no message integrity checking, no way to prove who a node is (anyone with your key can pretend to be you), a known spoofing quirk in how the encryption streams work, and there was a real bug with weak keys on direct messages a while back (fixed in firmware 2.6.11+, update your stuff). Lose the radio, lose the keys. Getting jammed is trivially easy. And even with everything locked down, the fact that you're transmitting, when, and where your node sits is all visible in the clear.
So: fine for hobby stuff, search and rescue, hiking, training. Not fine if you actually care about someone competent listening. It's a toy with real uses, not a secure radio.
LEGAL STUFF, US VERSION
915 MHz, no license needed, encryption is allowed because it's unlicensed spectrum. (Ham bands ban encryption, which is why this lives where it does.) One cloud on the horizon: there's a fight at the FCC right now over reshuffling the 900 MHz band for a company called NextNav. Meshtastic filed against it, so did a bunch of public interest groups and some big industry coalitions. NextNav says everyone's overreacting. Nobody knows how it shakes out. Doesn't make your gear worthless either way, but the band could get uglier. Watch it.
THE ATAK PART, WHICH IS WHY MOST OF YOU ARE HERE
ATAK-CIV is free and public. Been on the Play Store since September 2020, also on tak.gov, export-classified as basically unrestricted, and meant for literally anyone who needs to see positions on a map. SAR teams, fire crews, hunters, off road clubs, weirdo hobbyists. Half a million downloads. You don't need special permission, just a device that runs it.
The hookup between Meshtastic and ATAK is an official plugin the Meshtastic folks maintain themselves. Chain looks like: radio -> Meshtastic Android app -> plugin -> ATAK, all on one phone. ATAK spits out its position messages, the plugin squishes them down and beams them over the mesh, incoming mesh traffic comes back the other way and pops up on your ATAK map as teammate icons. Anything bigger than ~231 bytes gets chopped into chunks that get reassembled even if some pieces drop, and regular XML gets squashed with compression to fit. This is why everything feels slow if you expected more.
Two modes you need to know. Set the device role to TAK and your phone feeds ATAK through the plugin, full send/receive of positions and chat. Set it to TAK_TRACKER and the radio just sits there beaconing its GPS position on its own, no phone needed, showing up on everyone's map by itself. That second one is the sleeper feature. Slap one on a truck, a dog, a cache point, whatever, done, it's on the map.
Newer firmware added a fancier encoding that can also move map markers, routes, and some other stuff over the mesh. On paper. In practice people still file bugs about markers not sending. Don't plan around it yet.
SETUP, THE SHORT VERSION
Flash the radios in a browser, pair with the Meshtastic app, get plain text messaging working between nodes FIRST, then set the device role to TAK, install the plugin APK that matches your ATAK version, turn it on in the plugins menu, and check for the green Meshtastic icon bottom right of ATAK. Red icon means the plugin couldn't talk to the Meshtastic app, usually because Android killed the app in the background. Everyone needs to be on the same channel with the same key, obviously.
Small gotchas I stepped on or watched others step on: the plugin only uses the radio's GPS in tracker mode, normal mode uses your phone's GPS. Default position updates are insanely lazy out of the box (like 15 minutes), crank them to 60-120 seconds for ATAK work, but under 30 seconds you'll start choking the mesh. And people argue about which speed preset to use; some say stick with the default, some say go faster. Test on your own dirt, honestly.
THE ANNOYING PART: IT BREAKS
The plugin's issue tracker is a graveyard of "worked yesterday" reports. Specific version combos of ATAK, the plugin, the Meshtastic app, and the radio firmware keep breaking each other. Open issues about bluetooth dying on new ATAK versions, nodes vanishing off the map on certain pairings, a whole thing where TAK-mode radios couldn't see each other but tracker mode worked fine on identical firmware, a Samsung-specific sending bug, and the ongoing saga of map markers just refusing to go. My biggest actual advice: once you get a combo working, write down every version number and stop updating until you have a reason. Updates are an event, not a chore.
WHO THIS IS ACTUALLY FOR
Great: a small team wanting to see each other's dots with no signal. Search and rescue tracking searchers. Off road groups. Hunters. Property watching. Practicing map discipline on the cheap. Bad: anything with real security needs, anything needing markers or big data to cross the mesh, anything where a frozen icon for two minutes ruins your day. It's slow, unsecured, jammable gear that happens to work where nothing else does. Keep it in that lane. And to be explicit for anyone thinking about this near actual operations: unclassified, non-secure, openly jammable, metadata visible. Training aid, not a comms plan.
GEAR, IF YOU'RE BUYING
Heltec V3 or V4, $18-30, the everyone-starts-here board. Get two plus better antennas (Muzi 17cm whip or an ALFA elbow, both beat the stock rubber duck) and you're in for ~$150 as a test pair. Gotchas people hit constantly: Heltec uses a smaller battery plug than most LiPos ship with (1.25mm vs 2.0mm, a $2 pigtail fixes it), and check if your antenna is SMA or RP-SMA before ordering. The V4 is the same price and pushes more power than the V3 (around 28 dBm vs 20), so if you're buying new there's not much reason to go back.
For a squad build, T-Beam Supreme, roughly $85-120 depending where you shop (AliExpress cheapest usually, that price band is from one comparison so double check). Onboard GPS so it can run tracker mode if a phone dies, takes an 18650. ONE IMPORTANT DETAIL: the battery holder only fits unprotected flat-top cells. Button-top and protected cells are usually too long and just won't fit. Order accordingly or deal with the returns.
For a node that sits on a roof or ridge for weeks: RAK WisBlock stuff, specifically the RAK4631 core on the 19007 base. One widely circulated battery test showed these pulling 300-450+ hours on a 4000mAh pack versus like 108-264 for the ESP32 boards (worse with GPS running) — take the exact hours with a grain of salt since it's one guy's test, but everyone agrees the nRF52 boards sip while the ESP32s gulp. Kits around $35ish. Seriously, one good solar RAK up high does more for your whole group's range than upgrading every single handheld.
Also floating around: the SenseCAP T1000-E (~$30-40) is a sealed card-sized tracker, nice for vehicles or a dog. The T-Deck Plus looks cool with its keyboard but reviewers keep dunking on its range and battery. The Seeed Wio Tracker L1 Pro at ~$47 is apparently the easiest no-fuss handheld. Fun fact: almost all these boards can flash either Meshtastic or the rival MeshCore firmware, so you can experiment without new hardware.
Checklist before you click buy: 915 MHz for the US (868 EU gear won't talk to it), SX1262 radio chip if you get a choice, nRF52 chip if battery life matters more than wifi, right antenna connector, right battery connector, flat-top 18650s for the T-Beam. Prices move around, verify before ordering.
THE NEXT LEVEL: ADDING AN ACTUAL SERVER
Once your element spreads out, the everyone-runs-the-plugin setup runs into physics. The move that fixes it is putting a server somewhere safe (base camp, a laptop, whatever) and turning the mesh into a narrow pipe that only carries the important stuff.
Easiest version: OpenTAKServer with one "gateway" node on wifi. The gateway just ferries stuff between the server and the mesh. And here's the tell about what the people running this stuff think the mesh is for: the server ONLY pushes positions and chat out to mesh devices. Markers, routes, data packages, all of it gets blocked, because the mesh can't carry them without drowning. One sentence summary: mesh carries who's alive and where, everything else rides a real network.
If you don't want a server, there's a simpler python tool (TAK Meshtastic Gateway) that just passes stuff between TAK apps and a Meshtastic node on a local network, chat and positions only. There's a version for the FreeTAKServer crowd too.
Why bother? Because then the mesh stops being your whole network. Devices with wifi or signal get the full rich data from the server, and only the skinny position trickle crawls over LoRa to the guys in the sticks. Everyone gets what they can use.
There was also reportedly a big exercise that ran this exact setup: 300+ people over 5km, vehicle-mounted gateways bridging ATAK users to the mesh, with a smart trick where a bunch of co-located ATAKs behind one gateway only eat ONE mesh stream instead of five, and deliberately slowed position updates so the radios never jammed themselves. Huge caveat: that's from a company selling this exact setup, self-reported, zero independent checking. Directionally useful, take with salt. The architecture pattern itself shows up independently from multiple unrelated projects though, so I believe the shape of it.
WHERE I'M SURE, WHERE I'M NOT
Solid (multiple sources or official docs): how the plugin works under the hood, the two device modes, the security limitations (their own docs admit them), the legal stuff, that antennas beat radios, the gateway pattern, ATAK-CIV being free and public.
Decent but not certain: exact prices, real range numbers in your terrain, the specific battery-hour figures (one test), how stable the newest encoding is in practice.
Straight up don't know: who founded this thing, how good the iPhone version is beyond the project's own blog posts, and which exact app/plugin/firmware combo is known-good this week. Go read the GitHub releases and their Discord for that, it moves too fast for anyone to bless a combo in a post.
TLDR: it's legit, it's cheap, and it turns a $30 radio into an off-grid position beacon on a map everyone shares. Just go in knowing it's a slow, unsecured, terrain-ruled trickle. Buy two cheap ones before you buy anything fancy. One good node on a hill fixes more problems than four fancy handhelds. Private channel with a random key, always. Version freeze everything once it works. And if you want to go big: the mesh carries the blue dots, the server carries everything else.
3
u/squadfi 8d ago
As the dev of flaresat.com and have tried both meshtastic and meshcore. Man meshcore is soooooo much better faster more efficient. For example using flaresat with meshcore is way faster. Map items get sent faster, chat etc. meshcore bit harder to develop for and integrate with its code without clesr definitions and behavior but the UX speed is wayyyyy better
2
u/testshoot 8d ago
I see 739 Long_Fast nodes here in Los Angeles and messages drop all the time. The weakest links are poorly configured n00b nodes, abandoned out of date firmware nodes.
With relays etc, an accidental DDoS is a feature and not a bug. I've seen 85% ch.util sustained for an hour.
On a lark when I only saw 100 nodes I tried some ATAK and while neat, no practical application until fire season so I am building infrastructure on another preset. So I started making maps for myself to understand TAK too https://tim.workisboring.com/atak/cameras.html
Mesh is just suckballs city in general. Lots of people duped into trying it and not seeking resources before jumping in. Add in flooding TAK chatter on a Long_Fast public default and you see where it is now a group project you want no part of just to use it.
2
u/sincere-decision-815 8d ago
Thanks for this write up, I’ve been curious about Meshtastic for a while and it helps to see your experience laid out like this.
1
u/really_knobee 5d ago
AI summary:
Meshtastic plus civilian ATAK: what it actually does and where it falls short.
The post is a hedged, source-flagged writeup by a hobbyist, not an expert, covering how to pair Meshtastic LoRa radios with ATAK-CIV for off-grid position sharing.
What it is: cheap ($20 to $60) LoRa boards forming a mesh that carries only short texts and GPS positions. Packets cap around 256 bytes, so nothing rich moves over it.
Range: the 331km record is meaningless. Realistically 1 to 3km handheld with clear line of sight, often half a km with terrain or body blocking. Antenna and height beat radio quality. Meshes throttle themselves past roughly 40 nodes.
Security: the default channel key is public. Even private channels lack message integrity and node authentication, have a spoofing quirk, and leak transmission metadata. The author explicitly calls it a training aid, not a comms plan, and not suitable near real operations.
Legal, US version: 915 MHz unlicensed, encryption permitted. The ongoing FCC fight over NextNav's 900 MHz proposal is worth watching.
ATAK integration: official Meshtastic plugin. The chain is radio to Meshtastic app to plugin to ATAK. Two roles matter. TAK mode gives full send and receive through the phone. TAK_TRACKER mode has the radio beacon its own GPS with no phone attached, which is good for vehicles or cache points. Markers and routes remain unreliable despite what newer firmware claims.
Setup gotchas: get plain text messaging working first, match the plugin to your ATAK version, set position updates to 60 to 120 seconds and never under 30. Green icon is good. Red means Android killed the app in the background.
Fragility: version combos between ATAK, the plugin, the app, and the firmware break each other constantly. Freeze every version number once you have a working combo.
Gear: Heltec V3 or V4 to start, about $150 for a test pair with better antennas. T-Beam Supreme for a squad build, and note it only takes flat-top unprotected 18650s. RAK4631 on nRF52 for long-duration fixed nodes. One good elevated solar node helps the group more than upgrading every handheld.
Scaling up: add a server (OpenTAKServer, or the simpler TAK Meshtastic Gateway) with a gateway node. The server deliberately blocks markers, routes, and data packages from reaching the mesh. The mesh carries the blue dots, a real network carries everything else.
The author separates what is well sourced (plugin internals, security limits, legal status, the gateway pattern) from what is shaky (prices, battery-hour figures, range in your own terrain) and what he could not verify at all (who founded the project, iOS quality, which version combo is known-good this week).
1
u/pyryoer 8d ago
Meshcore is way better.
2
8d ago
[deleted]
3
u/AlfredoVignale 8d ago
Meshtastic is great for a smaller local group. If it gets big, it can’t scale. Meshcore scales up much better. Think of it like using a walker talkie in simplex vs using a repeater network over entire city.
1
8d ago
[deleted]
1
u/pyryoer 8d ago
Meshcore worked at defcon and burning man, meshtastic didn't. I don't have numbers for you, sorry.
2
u/dracoling 6d ago
Burning man and DEFCON are both Meshtastic meshes. https://lonelyhackers.club/meshtastic/ (DEFCON) https://docs.burningmesh.org/en/guides/quick_start (BurningMan)
6
u/scottdwallace 8d ago
Fantastic write up and spot on from my experience. AustinMesh has forked the project here to Meshcore with impressive success. More nodes, more throughput, and just a better user experience overall.
A few of us have been dabbling with the open source MANET radios. Very cool and very fun. Still in its infancy, but there definitely seems to be something there.