From: Steve Brown <sbrown@cortland.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: meshctl: set-pub fails
Date: Tue, 10 Oct 2017 10:04:35 -0600 [thread overview]
Message-ID: <1507651475.5470.1.camel@ewol.com> (raw)
discover-unprovisioned, provision, add-appkey & bind work as expected.
The meshctl's onoff client evokes expected behavior in zephyr's onoff
server.
The command being passed
set-pub 0100 c000 1 5 1000
The length of the set-pub packet exceeded the size of the data array in
struct mesh_pkt in net.c by 1. This stepped on the length field which
followed. The transmit mostly failed. The zephyr server received
nothing.
I extended the data array to 35. I now get consistent output. However,
the zephyr server is unable to decrypt with devkey. Net decrypt works,
but app decrypt fails.
I looked at how config-client.c:cmd_set_pub handled the app key index.
According to 4.3.2.16 (pg 158) of the Mesh Profile Spec, the app key
index should be in the top 12 bits of octet 4 & 5. I shifted it up by
4, but get the same results.
I'm pretty sure the problem is on the meshctl side. I've used the
Silabs Android app to successfully configure the zephyr server. It
successfully sends a set-pub which the zephyr server correctly handles.
Maybe this is a regression. Has set-pub worked in the past?
Any idea of where to go next?
Steve
next reply other threads:[~2017-10-10 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 16:04 Steve Brown [this message]
2017-10-10 22:30 ` meshctl: set-pub fails Steve Brown
2017-10-11 14:44 ` Steve Brown
2017-10-11 16:48 ` Gix, Brian
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=1507651475.5470.1.camel@ewol.com \
--to=sbrown@cortland.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.