bluez: linkkeys are not persisted across reboots

[PolarSolvent]

When you pair a device with bluez / bluetoothd running on openwrt, the keys are written in /var/lib/bluetooth/ which disappears when the tmpfs is cleared. This makes it impractical to use bluetooth. It would be better to package it with a bind mount or /var/lib/bluetooth symlinked to another persistent directory?

[PolarSolvent]

Something like this, but perhaps better if only root can read /etc/bluetooth/persist?

diff --git a/utils/bluez/Makefile b/utils/bluez/Makefile
index 363bf2c..c3410fc 100644
--- a/utils/bluez/Makefile
+++ b/utils/bluez/Makefile
@@ -144,6 +144,7 @@ define Package/bluez-daemon/install
        $(INSTALL_DIR) $(1)/etc/dbus-1/system.d/
        $(INSTALL_DATA) $(PKG_BUILD_DIR)/src/bluetooth.conf $(1)/etc/dbus-1/system.d/bluetooth.conf
        $(INSTALL_DIR) $(1)/etc/bluetooth
+       $(INSTALL_DIR) $(1)/etc/bluetooth/persist
        $(INSTALL_DATA) $(PKG_BUILD_DIR)/src/main.conf $(1)/etc/bluetooth/main.conf
        $(INSTALL_DATA) $(PKG_BUILD_DIR)/profiles/network/network.conf $(1)/etc/bluetooth/network.conf
        $(INSTALL_DATA) $(PKG_BUILD_DIR)/profiles/input/input.conf $(1)/etc/bluetooth/input.conf
diff --git a/utils/bluez/files/bluetoothd.init b/utils/bluez/files/bluetoothd.init
index 75f4d96..e8614f2 100644
--- a/utils/bluez/files/bluetoothd.init
+++ b/utils/bluez/files/bluetoothd.init
@@ -7,6 +7,7 @@ USE_PROCD=1
 PROG=/usr/bin/bluetoothd

 start_service() {
+       ln -snf /etc/bluetooth/persist/ /var/lib/bluetooth
        procd_open_instance
        procd_set_param command "$PROG" -n
        procd_close_instance

[diizzyy]

@hnyman @champtar @thess
Close this