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;
Subject: Re: bluez meshctl error: socket operation on non-socket
To:     "Gix, Brian" <brian.gix@intel.com>
Cc:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
References: <b260550e-0884-662d-e395-90e7678cb1a7@socoptimum.com>
 <78DAB7EA-B99D-4EDE-804B-7D127203DA1B@intel.com>
 <b332ed76-d5b1-c245-9301-3af578a274e4@socoptimum.com>
 <F3DC25C3-6C29-402B-B935-A4171B336403@intel.com>
From:   Venkat Vallapaneni <vallapaneni@socoptimum.com>
Message-ID: <f08116d3-4329-06a9-1b35-f8a7e4c8eff5@socoptimum.com>
Date:   Thu, 28 Nov 2019 22:41:24 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <F3DC25C3-6C29-402B-B935-A4171B336403@intel.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Brian,
I am using latest bluez and ell trees on ubuntu 18.04. Log windows 
showing segmentation fault if it helps. I ran demon first and then 
mesh-cfgclient

vallapaneni@venkat-laptop:~$ sudo ~/tools/bluez/mesh/bluetooth-meshd
D-Bus ready
Request name success
Loading node configuration from /var/lib/bluetooth/mesh
filter_set id: 1, --> 2b
filter_set id: 2, --> 29
filter_set id: 3, --> 2a
filter_set id: 4, --> 2b
Controller hci 0 is in use

vallapaneni@venkat-laptop:~/tools/bluez$ sudo 
~/tools/bluez/tools/mesh-cfgclient

Warning: config file "/home/vallapaneni/.config/meshcfg/config_db.json" 
not found
[mesh-cfgclient]# create
Segmentation fault
vallapaneni@venkat-laptop:~/tools/bluez$

Rgds,
Venkat.

On 28/11/19 9:37 pm, Gix, Brian wrote:
> Hi Venkat,
>
>> On Nov 28, 2019, at 2:59 AM, Venkat Vallapaneni <vallapaneni@socoptimum.com> wrote:
>>
>> ﻿Hi Brian,
>>
>> Thanks for the response. Yes, I am using PB-GATT barrier. With bluetooothd running, I am able to provision my device.
> Ok... well if this is specifically to play with Zephyr, you can build it to accept PB-ADV based provisioning as well. But i think Zephyrs mesh tip is PN-GATT by default.
>
>> I also tried mesh-cfgclient but unsuccessful. I launched the shell with mesh-cfgclient (with bluetooth-meshd running) and I gave create command in the shell. I see segmentation fault. Any steps I am missing?
> Are you on the tip of both the BlueZ tree, and the ELL tree? Also, what linux distro are you using?
>
>> Is mesh-cfgclient only for provisioning or also for sending mesh messages also?
> mesh-cfgclient not only provisions devices with PB-ADV, but it also is a full featured Config Client. It can send keys, bindings, subscriptions, and publications.
>
>
>> Rgds,
>>
>> Venkat.
>>
>>
>>> On 28/11/19 4:22 am, Gix, Brian wrote:
>>> Hi Venkat,
>>>
>>> Are you attempting to provision a device that requires PB-GATT provisioning?  If so, the bluetoothd daemon must be up and running. However, this tool is old, and will probably be deprecated at some point.
>>>
>>> However most Mesh devices should support Advertising based provisioning.
>>>
>>> The Mesh daemon (Bluetooth-meshd) and the mesh-cfgclient tool (in the tools directory) has been undergoing modification even since v5.52, so you will want to checkout the tip.
>>>
>>> ./tools/mesh-cfgclient is the tool most appropriate for mesh development today.
>>>
>>>
>>>
>>>>> On Nov 26, 2019, at 8:16 PM, Venkat Vallapaneni <vallapaneni@socoptimum.com> wrote:
>>>> ﻿Hi,
>>>>
>>>> I am trying to use bluez 5.52 for provisioning a bluetooth mesh capable device. When I gave provision <uuid>, I get this below error. Please let me know what I am missing.
>>>>
>>>> I am using ell 0.26 on ubuntu 18.04. I am able to provision successfully with bluez 5.50.
>>>>
>>>> AcquireWrite success: fd 8 MTU 69
>>>> GATT-TX:     03 00 10
>>>> *sendmsg: Socket operation on non-socket*[Zephyr]#
>>>>
>>>> Rgds,
>>>> Venkat.
>>>>
>>>>