Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp967616ybx; Thu, 7 Nov 2019 05:23:46 -0800 (PST) X-Google-Smtp-Source: APXvYqyBO4r6XOZaTwKMfOEjpXbbtAjvNV5sypzxZYral3FkLcOQPPRl1Sir6oLN+ll39rYuCRJX X-Received: by 2002:a17:906:f91:: with SMTP id q17mr690394ejj.113.1573133026035; Thu, 07 Nov 2019 05:23:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573133026; cv=none; d=google.com; s=arc-20160816; b=UAx8Eyczi888TZpNm4+Qtd/ZRgJrWuy5OGWGSuvssHhuG1l7xpfUXcOuKYBo4aoEZU CKpW/41qbvJrxsFIDrQzz9Vc9itNGpgrGYqxRmVfXODfLsnuoRqrplL6IvYqvvVG2Bde hXJXWdAqVjDXsUc7OSI+C4F/MyJyA8bY3o3n1DfZj/LnKkzX5V2gRAAtExXBUp6aGUlI 6vH2gLxE0mNnCT8jHnWTCAM+8KUuzCPwqmFd/goLOV3m4njM74yA92l1Z9MfMSDohI4b Beg1oMCItZDja4sCYngu3WdebEEvEjc9UPr2qvhVFFIr02EVWhulGodvsDgKtKmeqEzm eLnA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:to:from:date; bh=jzUQyCFJcdQOE6EWvMLuAdnhMc3PN0ip1NEfGum5G4A=; b=TObB3ePgsDu6dZeNWO0PAhhMiU4x1HeXQduFuvQKM23Z4qxjzY60/FHtVFRhDNOCKz 7NiCL6i2vC7OoRxRHvOSBkPqSIRV/lJQzGn7qYhv4bVFbTCHvuDxqpEuBd4rZTFgkCh3 6JT7/OA2KPqidMG99zBQps+EGi/ivntP580+bvj+E4Rp3AH/NRmWJIzxDRHgiIEBBpAI NB6NGTQwPj7p0yppTLe0mA/anBblIas9JOJ63O08FcSkc5zUwPTTKad1M2pmTkm4LzZd n86xeGjZ3ISvfFiVFVZPEwsxgVot9ozxyBpjq8ET63lsBm1XhW+MzbgVkGn3yakp6WbG SP/A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b9si1430582eda.115.2019.11.07.05.23.09; Thu, 07 Nov 2019 05:23:46 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388008AbfKGNXB (ORCPT + 99 others); Thu, 7 Nov 2019 08:23:01 -0500 Received: from hall.aurel32.net ([195.154.113.88]:41556 "EHLO hall.aurel32.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730980AbfKGNXB (ORCPT ); Thu, 7 Nov 2019 08:23:01 -0500 Received: from [2a01:e35:2fdd:a4e1:fe91:fc89:bc43:b814] (helo=ohm.rr44.fr) by hall.aurel32.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iShka-0004AO-A6 for linux-bluetooth@vger.kernel.org; Thu, 07 Nov 2019 14:23:00 +0100 Received: from aurel32 by ohm.rr44.fr with local (Exim 4.92.3) (envelope-from ) id 1iShkZ-0007IP-VG for linux-bluetooth@vger.kernel.org; Thu, 07 Nov 2019 14:22:59 +0100 Date: Thu, 7 Nov 2019 14:22:59 +0100 From: Aurelien Jarno To: linux-bluetooth@vger.kernel.org Subject: Bluez mesh-cfgclient: provisioning not working with OOB number/string Message-ID: <20191107132259.GA26507@aurel32.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi, I gave a try to the new mesh-cfgclient tool addition, that's a really nice addition. I have tried to provision a Zephyr based Bluetooth Mesh node, basically the Mesh OnOff Model sample for the nRF52 chip [1]. Unfortunately I have not been able to provision it, it fails around the string OOB authentication: | [mesh-cfgclient]# discover-unprovisioned on | Unprovisioned scan started | Scan result: | rssi = -73 | UUID = ECB1EC84E1E500000000000000000000 | Scan result: | rssi = -57 | UUID = ECB1EC84E1E500000000000000000000 | Scan result: | rssi = -56 | UUID = ECB1EC84E1E500000000000000000000 | [mesh-cfgclient]# provision ECB1EC84E1E500000000000000000000 | Provisioning started | Provisioning failed: | UUID = ECB1EC84E1E500000000000000000000 | bad-pdu | [mesh-cfgclient]# On the Zephyr node, the OOB string has been correctly displayed: | uart:~$ OOB String P4Z77K I have tried also with an OOB number, it also failed the same way. I have then tried doing a provisioning with OOB authentication and it worked fine. After that everything I tried in the mesh-cfgclient tool worked as expected: adding appkey, binding it, getting/setting the subscription list and the publish address, etc. Note that provisioning works fine even with OOB string/number using meshctl and the GATT provisionner. Any idea what is the issue and how to debug it? Thanks, Aurelien [1] https://docs.zephyrproject.org/latest/samples/boards/nrf52/mesh/onoff-app/README.html -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net