l2ping with threads.

Flood a given bluetooth device with ping requests in order to force it to disconnect.

Satisfy the dependencies first, and then:

git clone https://github.com/kovmir/l2flood
cd l2flood
make # Use `make serial` to build upstream l2ping.
sudo make install

Suppose there is a loud bluetooth speaker in public, and suppose 94:3a:2c:e1:2b:07 is its address. You can shut it off like that:

l2flood 94:3a:2c:e1:2b:07 # Flood with as much threads as there are CPU cores.
l2flood -n 50 94:3a:2c:e1:2b:07 # Flood with 50 threads.

A weak speaker CPU will not be able to process that many ping requests, and music decoding simultaneously; so it will disconnect.

Keep in mind:

• The default delay between packets has been changed to 0.
• The default data packet size has been increased to 600.
• l2ping options work.
• Your bluetooth card is your bottleneck: Even if you have a multi-core multi-gigahertz CPU, it makes little to no sense to spawn as much as 1,000 threads, because your bluetooth card is unlikely to be fast enough to process all the requests as quick as you submit them.

• Bluez
  • On Debian/Ubuntu/Kali sudo apt install -y libbluetooth-dev.

• Linux

Q: Does it work in termux?

A: No, Bluez libraries are not available in termux.

Q: Does it work on Steam Deck?

A: Yes.

Q: How to increase flood efficiency?

A: Get a second bluetooth card, and flood using both of them.

BT_ADDR='00:00:00:00:00:00' # Set the target address.
l2flood -i hci0 $BT_ADDR
l2flood -i hci1 $BT_ADDR

Q: How to fix Can't create socket: Operation not permitted?

A: Re-run as root user.