Hi Cathy, > The Connman is V0.5. I'm sure there are several bluetooth devices > around by "hcitool scan". > I tried to scan the bluetooth devices around by device.ProposeScan(), > but failed to list any when call GetProperties() of Bluetooth Network > interface. > > I want to confirm with you that is the proper way to detect bluetooth > device around and set up PAN connection with other bluetooth device is > similar to WiFi connection as below: > 1. Scan and get bluetooth devices around (may show bdaddr to user)
in the Bluetooth case you can't just do the scanning like this. You have to setup the device via BlueZ first. Then it will list it. So you would have to use CreateDevice or CreatePairedDevice from BlueZ to make the device available to ConnMan. Either use bluetooth-wizard or test-device from the BlueZ test scripts for this. > 2. Choose one bluetooth device for PAN connection There are still some details missing to get this working without any troubles. You need a device with PAN support and NAP UUID. > 3. Set the static IP address on local device and peer device There is no concept for local and peer device. Bluetooth networks are working differently. You just get a bnep0 interface that is directly attached to the remote device. In the client case (with ConnMan) this is a point-to-point connection with the MAC address of the peer device. In case of NAP, then ConnMan also uses DHCP for the address assignment. When using GN then link-local addresses (aka Avahi) have to be used. > 4. Show connection information by GetProperties of Connection > interface. Once the NAP connection works smoothly then these should show up as ConnMan connections. Also with Bluetooth you get a 1:n model. This is different to WiFi. One Bluetooth adapter can connect multiple remote device at the same time. Regards Marcel _______________________________________________ connman mailing list [email protected] https://lists.moblin.org/mailman/listinfo/connman
