A MeshCore Network, Built by Texans
A community-run MeshCore LoRa radio network spanning Texas — no internet, no cell towers, no infrastructure required. Just radios talking to radios.
A community-run MeshCore LoRa radio network spanning Texas — no internet, no cell towers, no infrastructure required. Just radios talking to radios.
MeshCore devices use long-range LoRa radio to send encrypted messages between nodes — covering several miles per hop with affordable hardware.
Every node is a relay. Messages automatically find their way through the network, routing around outages without any central server.
All traffic is end-to-end encrypted using public-key cryptography. Each device generates its own identity — no accounts, no registration.
Runs on battery or solar. When cell towers and internet go down — storms, disasters, grid failures — the mesh keeps working.
Live packet visualization, node tracking, route analysis, and deep mesh analytics for the Texas network. Powered by CoreScope.
Coverage map for the San Antonio region. Shows confirmed BIDIR, TX, RX, and DISC observations from wardriving and fixed observers.
The MeshTexas broker accepts connections from any Texas-area MeshCore observer. Auth uses the same JWT model as MeshMapper and Waev — your device signs its own token from its keypair. No credentials or registration required.
mqtt.meshtexas.net
443
WebSocket Secure (WSS)
JWT — auto, from device keypair
Select the software your observer is running:
For Heltec V3/V4, T-LoRa, Tracker, and any ESP32-based board running the agessaman MeshCore firmware with MQTT bridge support.
Connect via USB serial at 115200 baud using a terminal (PuTTY, screen, minicom) or the MeshCore serial console.
Open the MeshCore companion app, connect to your device over Bluetooth, then navigate to Remote Management → Command Line — all commands below are entered there, no USB cable needed.
SAT San Antonio
AUS Austin
HOU Houston
DFW Dallas–Fort Worth
ELP El Paso
ABI Abilene
AMA Amarillo
MFE McAllen
SJT San Angelo
TXK Texarkana
CT Central Texas
set mqtt.iata SATget mqtt1.preset through get mqtt6.preset and use one that shows none.
mqtt1 with your chosen slot:
set mqtt1.preset custom
set mqtt1.server mqtt.meshtexas.net
set mqtt1.port 443
set mqtt1.audience mqtt.meshtexas.net
save
rebootget mqtt.statusmqtt1: connected.
For RAK4631 and any serial-connected MeshCore device running meshcoretomqtt.
/etc/mctomqtt/config.d/ on Linux.
SAT with the Texas city nearest to you, then expand the option that matches your setup:
SAT San Antonio
AUS Austin
HOU Houston
DFW Dallas–Fort Worth
ELP El Paso
ABI Abilene
AMA Amarillo
MFE McAllen
SJT San Angelo
TXK Texarkana
CT Central Texas
Sets IATA only for the MeshTexas broker — safe when you're also connected to other regional meshes. Create 30-texasmesh.toml in config.d/:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.net"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.net"
[broker.topics]
iata = "SAT"Simpler option — sets IATA globally. Create or edit /etc/mctomqtt/config.d/99-user.toml:
[general]
iata = "SAT"Then create 30-texasmesh.toml in config.d/ without a [broker.topics] block:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.net"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.net"sudo systemctl restart meshcoretomqtt
journalctl -u meshcoretomqtt -fRun ls /etc/mctomqtt/config.d/ to see what files already exist before picking a number.
For any MeshCore observer running meshcore-packet-capture.
SAT with the Texas city nearest to you, then expand the option that matches your setup:
SAT San Antonio
AUS Austin
HOU Houston
DFW Dallas–Fort Worth
ELP El Paso
ABI Abilene
AMA Amarillo
MFE McAllen
SJT San Angelo
TXK Texarkana
CT Central Texas
Sets IATA only for the MeshTexas broker — safe when you're also connected to other regional meshes. Create meshtexas.toml in your presets directory:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.net"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
iata = "SAT"
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.net"Simpler option — sets IATA globally. Create or edit /etc/meshcore-packet-capture/config.d/99-user.toml:
[general]
iata = "SAT"Then create meshtexas.toml in your presets directory without an iata line:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.net"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.net"After connecting, search for your node name on the MeshTexas Analyzer. It should appear within a few minutes of your device sending its first advert packet.
Open Analyzer ↗MeshTexas is active across Texas. Coverage grows as more operators add nodes and repeaters. IATA city codes are used to identify regions on the network.
Other Texas mesh radio communities and resources.