Multicast is the default output and needs no change on the unit. Detections and unit health arrive as Cursor on Target on any TAK client that shares a network segment with the unit.
On the TAK device
| Client | Setting |
|---|---|
| ATAK | Settings → Network Preferences → SA Multicast: set both Input and Output to 239.2.3.1:6969 |
| iTAK | SA Multicast input 239.2.3.1:6969 |
| WinTAK | Settings → Network → add multicast input 239.2.3.1:6969 |
The device must be on the same network segment as the unit — the unit’s hotspot, or the same LAN. Multicast does not cross routers, VPNs, or cellular links; for those, use a TAK Server.
What you will see
Each detected aircraft appears as a drone icon with position, altitude, speed, heading, pilot location, and home point where the protocol provides them. The unit itself appears as a marker at its own GPS position with health data in the remarks.
Note The unit sends multicast on every active interface and rechecks about every 30 seconds. A device that joins the hotspot mid-session is picked up without a restart.
Update rate
Each aircraft is limited to one update every 2 seconds by default. For large numbers of aircraft or a constrained link, raise rate_limit in /home/dragon/DragonSync/config.ini and restart dragonsync.
Nothing showing in ATAK
- Confirm the device and the unit share a network segment. On the hotspot, confirm the device has a
192.168.12.xaddress. - Confirm multicast is enabled and the address is correct in
config.ini. - Confirm the output service is running and the API answers from the device’s network:
sudo systemctl status dragonsync
curl http://<wardragon-ip>:8088/status- Confirm traffic is actually leaving the unit:
sudo tcpdump -i any host 239.2.3.1 and port 6969- Review the output log for TAK errors:
journalctl -u dragonsync | grep -i takIf traffic leaves the unit and the device still shows nothing, the problem is on the device or the network between them — a client-isolation setting on a Wi-Fi access point is a common cause.
Going further
Richer unit health and track detail inside ATAK: Installing the WarDragon ATAK Plugin. Centralized, multi-user, or off-segment operation: Connecting to a TAK Server.
Related
- WarDragon User Guide, Section 8.1 — multicast
- WarDragon User Guide, Section 8.4 — reducing network load
- WarDragon User Guide, Section 10.6 — TAK troubleshooting