Skip to content

Latest commit

 

History

History
109 lines (72 loc) · 4.13 KB

README.md

File metadata and controls

109 lines (72 loc) · 4.13 KB

Attention

As of Nov 2024, the SniffleToTAK repo is out of date and has now morphed into the following repo with most recent updates being under the main branch.
https://github.com/alphafox02/DragonSync/

SniffleToTAK

SniffleToTAK is a proxy tool that bridges the gap between the Sniffle Bluetooth 5 long range extended sniffing and the TAK (Team Awareness Kit) system. This tool allows users to utilize a Sniffle compatible dongle to detect Bluetooth 5 long range extended packets and relay them to TAK servers or multicast them on a network for ATAK (Android Team Awareness Kit) devices.

Features

  • Leverages the Sniffle fork from Sniffle GitHub.
  • Supports ZeroMQ (ZMQ) for data transmission.
  • Converts ZMQ messages to Cursor on Target (CoT) format.
  • Provides integration with ATAK devices for Bluetooth Remote ID drone detection and monitoring.

Requirements

  • Sniffle compatible dongle
  • ATAK device
  • Python 3

Setup and Usage

Clone the Sniffle Fork

git clone https://github.com/bkerler/Sniffle
cd Sniffle

Run the Sniffle Receiver

python3 Sniffle/python_cli/sniff_receiver.py -l -e -z --zmqhost 0.0.0.0 --zmqport 12345

This command configures the Sniffle dongle to look for Bluetooth 5 long range extended packets and forwards them via ZeroMQ (ZMQ).

Start the SniffleToTAK Proxy with the Correct ZMQ Details

Without TAK Server Information (Multicast Only)

python3 sniffletotak.py --zmq-host 0.0.0.0 --zmq-port 12345

With TAK Server Information

python3 sniffletotak.py --zmq-host 0.0.0.0 --zmq-port 12345 --tak-host <tak_host> --tak-port <tak_port>

Enable Debug Logging

python3 sniffletotak.py --zmq-host 0.0.0.0 --zmq-port 12345 -d

Replace <tak_host> and <tak_port> with the appropriate values for your setup.

Verify Multicast Reception on ATAK

Ensure that your ATAK device is connected to the same network as the machine running SniffleToTAK. If configured correctly, ATAK should receive the multicast CoT messages and display the drone information on the map.

How It Works

  1. The Sniffle compatible dongle captures Bluetooth 5 long range extended packets.
  2. The captured packets are sent to the Sniffle receiver script which forwards them via ZeroMQ (ZMQ).
  3. The SniffleToTAK proxy receives the ZMQ messages and translates them into CoT format.
  4. The CoT messages are sent to a TAK server or multicast to the network for ATAK devices to detect and monitor drones.

Example Command

To start the SniffleToTAK application with ZMQ server running on 127.0.0.1 port 12345, sending multicast to ATAK:

python3 sniffletotak.py --zmq-host 127.0.0.1 --zmq-port 12345

Troubleshooting

  • No Data on ATAK:

    • Ensure the ATAK device is on the same network as the SniffleToTAK machine.
    • Verify that multicast traffic is allowed on your network.
    • Check if the correct ZMQ host and port are used.
  • Debugging:

    • Use the -d flag to enable debug logging for more detailed output.
    • Use network monitoring tools like Wireshark to verify multicast traffic.

License

MIT License

© 2024 cemaxecuter

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.