TCP PROXY
STOPPED
RADIO
⬡ Overview
⬡ Sessions 0
⬡ Live 0
⬡ Protocol Log 0
⚙ Config
? Help
Traffic Flow — packets/sample (15s)
— →clients — →radio
Active Sessions
◌
No sessions yet
Sessions persist across reconnects · keyed by IP · text messages queued while offline
◌
No sessions yet — connect the Meshtastic app
Live TCP connections — updates every 5s
◌
No clients connected
All Handshake TX RX Sessions Replays Errors auto
◌
No log entries
Proxy Configuration
Network
Port
Default 4403. If MeshDash connects to the radio via TCP on 4403, use 4404 here.
Bind Host
Max Clients
Radio Slot
Slot
Which MeshDash radio connection to proxy.
Sessions
Session TTL (s)
How long to retain an offline session before purging. Default 7200 (2h).
Queue Max (msgs)
Max text messages to buffer per offline session for replay on reconnect.

### What is TCP Proxy?

TCP Proxy allows you to connect the official Meshtastic mobile app (or other TCP-compatible clients) directly to your MeshDash dashboard. It creates a bridge so your app thinks it is connected directly to a physical radio.

### How to Connect

- Open the Meshtastic App on your phone.
- Go to Settings → Radio Configuration → Connection (or Network/TCP).
- Enter the IP address of your MeshDash server.
- Enter the configured port (if not using the default 4403).
- The app will connect, sync nodes, and receive live messages.

### Configuration Options

ℹ
Port: The network port the proxy listens on. Default is 4403. If your physical radio is using 4403 on the same network, change this to 4404.
ℹ
Max Clients: The maximum number of simultaneous app connections allowed.
ℹ
Session TTL & Queue: How long the proxy remembers a disconnected device, and how many messages to buffer. When the app reconnects, missed messages are delivered.
⚠
Cloudflare Tunnels: Raw TCP connections are not supported through standard Cloudflare web tunnels without additional configuration. Use a local IP, VPN (Tailscale), or port forwarding.