Hi Stefan, > I recently added a Bluetooth dongle to a RS232 device to get readouts > from a remote location. This is working fine as long as I execute > "rfcomm bind" after each restart. > > However, when I wanted to automate this process by using a rfcomm.conf > file as suggested by several guides on the web [1], I realized that the > corresponding code has been removed from the rfcomm tool several years > ago [2]. > > I tried to use udev as a replacement by writing a rule which executes > rfcomm after pairing, but it seems like sysfs does not expose > information about coupled devices (udevadm info -a -p > /sys/class/bluetooth/hci0). > > Is it possible to solve that problem using udev? Or are there any other > best practices? Thank you for your consideration. just create an init script of systemd service file and run the rfcomm bind command manually. As long as you know the remote BD_ADDR of the device you want to connect to and the RFCOMM channel of the SSP service on that device, you can create a binding. No local controller has to be present to create a RFCOMM binding. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
