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: Wed, 27 Nov 2019 22:52:01 +0000 [thread overview]
Message-ID: <78DAB7EA-B99D-4EDE-804B-7D127203DA1B@intel.com> (raw)
In-Reply-To: <b260550e-0884-662d-e395-90e7678cb1a7@socoptimum.com>
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.
>
>
next prev parent reply other threads:[~2019-11-27 22:52 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 [this message]
2019-11-28 10:58 ` Venkat Vallapaneni
2019-11-28 16:07 ` Gix, Brian
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=78DAB7EA-B99D-4EDE-804B-7D127203DA1B@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;
as well as URLs for NNTP newsgroup(s).