From: Jamie Mccrae <Jamie.Mccrae@lairdconnect.com>
To: Steve Brown <sbrown@ewol.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: RE: mesh: scan params specify random address, but no random address set
Date: Mon, 13 Jan 2020 07:30:35 +0000 [thread overview]
Message-ID: <DM5PR14MB1385927CD0D2A8B1D0ADBB15E6350@DM5PR14MB1385.namprd14.prod.outlook.com> (raw)
In-Reply-To: <988d501619da548fff95f1f1afaa6456e18e6dfe.camel@ewol.com>
> I'm using the Zephyr hci implementation on a bt dongle. It complains
> that no random address is set when scan enable is sent.
>
> My RPi doesn't care if a random address is set or not.
>
> Steve
Hi Steve,
You need an address set because of directed advertising. You need to update your zephyr project to include a random, address, this is covered quite extensively on the zephyr documentation and discussions for Nordic chipsets.
Thanks,
Jamie
THIS MESSAGE, ANY ATTACHMENT(S), AND THE INFORMATION CONTAINED HEREIN MAY BE PROPRIETARY TO LAIRD CONNECTIVITY, INC. AND/OR ANOTHER PARTY, AND MAY FURTHER BE INTENDED TO BE KEPT CONFIDENTIAL. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE DELETE THE EMAIL AND ANY ATTACHMENTS, AND IMMEDIATELY NOTIFY THE SENDER BY RETURN EMAIL. THIS MESSAGE AND ITS CONTENTS ARE THE PROPERTY OF LAIRD CONNECTIVITY, INC. AND MAY NOT BE REPRODUCED OR USED WITHOUT THE EXPRESS WRITTEN CONSENT OF LAIRD CONNECTIVITY, INC.
prev parent reply other threads:[~2020-01-13 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 14:09 mesh: scan params specify random address, but no random address set Steve Brown
2020-01-13 7:30 ` Jamie Mccrae [this message]
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=DM5PR14MB1385927CD0D2A8B1D0ADBB15E6350@DM5PR14MB1385.namprd14.prod.outlook.com \
--to=jamie.mccrae@lairdconnect.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sbrown@ewol.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).