Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Shaik Mahaboob Nazeer <nazeer.m@phytec.in>
To:     linux-bluetooth@vger.kernel.org
Cc:     Jonas Remmert <j.remmert@phytec.de>
Subject: Issue with mesh provisioning.
Message-ID: <33a1f056-12c2-1aaa-4172-ea1fba341428@phytec.in>
Date:   Tue, 14 May 2019 14:50:26 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

hi,

-> We tried Zephyr Mesh onoff example on nrf52 eval kit to test the Mesh Functionality.For provisioning of the node
   we are using meshctl, built from the latest current master of the bluez source.So during the provisioning of the node when we
   start the "meshctl" and run the "discover-unprovisioned on" we are able to get the Device UUID for the provisioning.

   Later when we try to provision the node using the "provision <UUID>" command it initiate the provision and does not wait
   for the user to enter OOB .You can find the log as below.
   /*******************************************/
   $meshctl
   Waiting to connect to bluetoothd...Reading prov_db.json and local_node.json
   from /home/nazeer/.config/meshctl directory
   [meshctl]# discover-unprovisioned on
   SetDiscoveryFilter success
   Discovery started
   Adapter property changed
   [CHG] Controller 00:1B:DC:06:96:17 Discovering: yes
             Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
             Device UUID: 81f5d3bd49fa00000000000000000000
             OOB: 0000
   [meshctl]# provision 81f5d3bd49fa00000000000000000000
   Trying to connect Device FA:49:BD:D3:F5:81 Zephyr
   Adapter property changed
   [CHG] Controller 00:1B:DC:06:96:17 Discovering: no
   Connection successful 
   Services resolved yes
   Found matching char: path
   /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0011, uuid
   00002adb-0000-1000-8000-00805f9b34fb
   Found matching char: path
   /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0013, uuid
   00002adc-0000-1000-8000-00805f9b34fb
   Start notification on
   /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0013
   Characteristic property changed
   /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0013
   AcquireNotify success: fd 7 MTU 69
   Notify for Mesh Provisioning Out Data started
   Open-Node: 0x55aca5ac1220
   Open-Prov: 0x55aca5abfb40
   Open-Prov: proxy 0x55aca5ac3d10
   Initiated provisioning
   Characteristic property changed
   /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0011
   AcquireWrite success: fd 8 MTU 69
   GATT-TX:     03 00 10
   GATT-RX:     03 01 04 00 01 00 00 06 00 18 00 00 00
   Got provisioning data (12 bytes)
                01 04 00 01 00 00 06 00 18 00 00 00
   GATT-TX:     03 02 00 00 02 04 06
   GATT-TX:     03 03 76 4a b7 61 52 e1 72 9c b0 cc 95 ad 62 22
   GATT-TX:     8b 65 8f 2a dd 2c 79 a0 ec 5e 8e db a5 65 1b 76
   GATT-TX:     dd cf 63 4d 17 aa a0 a4 ea d4 5e 17 2e a6 18 8e
   GATT-TX:     19 83 56 97 cd c9 81 50 15 ff 47 37 de 92 3a 80
   GATT-TX:     30 64
   [Zephyr]#
  /********************************************/

-> Later we tried to remove the OOB security from the zephyr onoff code and tried to do provisioning again,linux-bluetooth@vger.kernel.org 
   but this time it completely fails to start provisioning.Please find the log as below
  /**********************************/
  meshctl]# provision 81f5d3bd49fa00000000000000000000
  Trying to connect Device FA:49:BD:D3:F5:81 Zephyr
  Adapter property changed
  [CHG] Controller 00:1B:DC:06:96:17 Discovering: no
  Connection successful
  Services resolved yes
  Found matching char: path
  /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0011, uuid
  00002adb-0000-1000-8000-00805f9b34fb
  Found matching char: path
  /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0013, uuid
  00002adc-0000-1000-8000-00805f9b34fb
  Start notification on
  /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0013
  Characteristic property changed
  /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0013
  AcquireNotify success: fd 7 MTU 69
  Notify for Mesh Provisioning Out Data started
  Failed to start provisioning
  Attempting to disconnect from FA:49:BD:D3:F5:81
  Characteristic property changed
  /org/bluez/hci0/dev_FA_49_BD_D3_F5_81/service0010/char0013
  Services resolved no
  [meshctl]#
  /**************************************/

Could you elaborate a little on the status of the current master of bluez in regards to BLE mesh, is it usable or should we look to older versions?

Do you know if there is a common issue while provisioning of the node with the current master and
is there anything that need to be configured before provisioning? 

-- 
Thanks and Regards