Hi all, Am 31.12.19 um 18:35 schrieb Stefan Seyfried: > Hi Marcel, > > thanks for the response. > > Am 26.12.19 um 21:40 schrieb Marcel Holtmann: > >>> So is there a way to set up a rfcomm device via bluetoothctl? I could >>> not find one, but maybe I did not look hard enough? >>> >>> If not, could we please un-deprecate rfcomm, because having everyone out >>> there reinvent the functionality in crazy ways probably is not a good idea. >>> >>> Or should I just continue to build the package with --enable-deprecated? >>> But that will ship tools with known unfixed security issues (hcidump). >> >> have a look at doc/profile-api.txt. > > This would be for creating a "rfcomm service" for other devices to > connect to, right? (The equivalent of "rfcomm listen...") > > But how would I connect e.g. to my serial module (I got this for trying > it by myself instead of relying on bugreporters results...), so what's > the dbus equivalent of "rfcomm connect hci0 <bdaddr> <channel>"? OK, now I found https://github.com/tonyespy/bluez5-spp-example which explains how to do this. I'd still think an example in the bluez documentation would be useful, because... > the knowledge on how to handle this seems > non-existent: all the various bluetooth codebases checked (e.g. blueman, > pybluez) just re-implement the code in tools/rfcomm.c's cmd_connect > (socket, bind, connect, ioctl RFCOMMCREATEDEV, ...). Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
