From: Brian Gix <bgix@codeaurora.org>
To: "Ganir, Chen" <chen.ganir@ti.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: LE SM Testing
Date: Sun, 18 Dec 2011 09:16:21 -0800 [thread overview]
Message-ID: <4EEE1FE5.80204@codeaurora.org> (raw)
In-Reply-To: <F0070FBC0FB3174D8D11444EB2D5B02607D2C752@DNCE02.ent.ti.com>
Hi Chen,
On 12/18/2011 4:19 AM, Ganir, Chen wrote:
> Hi.
> Does anyone have an idea how can I establish an LE link with SM fixed channel to a remote peer to test the SMP functionality ? I do not see any possibility to do this at the moment. Hcitool does not connect the SMP, and btiotest requires a remote l2cap channel listener other than the SMP. Gatttool will not help as well, since it requires an ATT server at the peer device.
Fixed channels (including the LE fixed channels) require no setup beyond
ACL establishment. So you can "establish" the SM channel simply by
creating an LE link.
Using gatttool -I, you can establish a connection a connection to a
remote LE device. SM functionality can then be triggered by elevating
security. ("sec-level medium" from gatttool). This should be the
equivilent of "General Bonding" in the BR/EDR world.
I think hcitool also has an "lecc" command that specifically calls the
"Create LE connection" HCI command, which could be used if you just need
to establish an LE connection.
Also, hasn't the "pair device" via the MGMT interface been
implemented/enabled in BlueZ? This would be the "Dedicated Bonding"
equivalent of BR/EDR.
--
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
prev parent reply other threads:[~2011-12-18 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 12:19 LE SM Testing Ganir, Chen
2011-12-18 17:16 ` Brian Gix [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=4EEE1FE5.80204@codeaurora.org \
--to=bgix@codeaurora.org \
--cc=chen.ganir@ti.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 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).