public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: Venkat Vallapaneni <vallapaneni@socoptimum.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez meshctl error: socket operation on non-socket
Date: Thu, 28 Nov 2019 16:07:57 +0000	[thread overview]
Message-ID: <F3DC25C3-6C29-402B-B935-A4171B336403@intel.com> (raw)
In-Reply-To: <b332ed76-d5b1-c245-9301-3af578a274e4@socoptimum.com>

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.
>>> 
>>> 

  reply	other threads:[~2019-11-28 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27  4:16 bluez meshctl error: socket operation on non-socket Venkat Vallapaneni
2019-11-27 22:52 ` Gix, Brian
2019-11-28 10:58   ` Venkat Vallapaneni
2019-11-28 16:07     ` Gix, Brian [this message]
2019-11-28 17:11       ` Venkat Vallapaneni
2019-11-28 23:05         ` Steve Brown
2019-11-29  1:28           ` Venkat Vallapaneni
2019-12-03 23:42           ` Stotland, Inga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F3DC25C3-6C29-402B-B935-A4171B336403@intel.com \
    --to=brian.gix@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vallapaneni@socoptimum.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox