Expand description
Linux BLE from pure Rust, with no dependencies.
Two ways to reach a controller, because Linux offers two:
bluez— the supported path, overdbustoorg.bluez. Pairing, bonding and agents are the daemon’s problem.hci+gatt— no daemon at all. ATT over an L2CAP socket for GATT, a raw HCI socket for scanning.
Neither binds a C library. D-Bus is a wire protocol over a Unix socket and
is spoken as one; ATT, HCI and L2CAP are kernel sockets reached through
sys.
dbus::codec, dbus::value and att are pure byte manipulation and
build everywhere, so the parts where the bugs live — alignment, truncation,
signature-directed decoding — are unit-tested on any host rather than only
inside a container.
§License
MIT — Copyright © 2025 Eugene Hauptmann
Modules§
- att
- The Attribute Protocol.
- bluez
- The BlueZ object model.
- dbus
- A D-Bus client and server, spoken directly.
- gatt
- A GATT client over an L2CAP socket, with no daemon in the way.
- hci
- LE scanning. The advertising-data parser is portable; only the raw socket inside it is Linux-only. LE scanning over a raw HCI socket.
- l2cap
- L2CAP connection-oriented channels, as Bluetooth sockets.
- peripheral_
backend - The Linux peripheral engine: a GATT application exported over D-Bus.
- sys
- The Bluetooth socket family.