Hi Jon, On Mon, Jan 25, 2016 at 7:53 PM, Jon Hoffman <Jon.Hoffman@xxxxxxxxxxxxxxxx> wrote: > I do not want to use Bluez 4.XX so I am attempting to get this to work with Bluez 5 on both the master and slave. I have tried the following commands on both the Raspberry Pi with Bluez 5.23 and Fedora 23 with Bluez 5.35 BlueZ 4 is too old to support, if you want some support from the community just stick with BlueZ 5. > > Slave (Raspberry Pi Bluez 5.23 or Fedora 23 Bluez 5.35): > #need root access > sudo su > > #enable 6lowpan over Bluetooth le > echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enabled > > #start advertising Bluetooth LE service > hciconfig hci0 leadv There is a built-in D-Bus interface to advertise using bluetoothd, or if you prefer low level then use btmgmt. > master (Raspberry Pi Bluez 5.23 or Fedora 23 Bluez 5.35): > #need root access > sudo su > > #enable 6lowpan over Bluetooth le > echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable > > #establish le connection to master > hcitool lecc 5C:F3:70:XX:XX:XX > > echo "connect 5C:F3:70:XX:XX:XX 1" > /sys/kernel/debug/bluetooth/6lowpan_control This actually works for me so perhaps there is something else going on, you can try enabling dynamic debug in your kernel as well as checking the HCI trace, perhaps the L2CAP channel doesn't connect or something like that. -- Luiz Augusto von Dentz -- 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
