From: Mallikarjun Phulari <p.mallikarjun@globaledgesoft.com>
To: Maxime CHEVALLIER <maxime.chevallier@smile.fr>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] tools/btgatt-client: Fix set-security interactive command
Date: Tue, 31 Jan 2017 16:00:39 +0530 (IST) [thread overview]
Message-ID: <306265495.518366.1485858639832.JavaMail.zimbra@globaledgesoft.com> (raw)
In-Reply-To: <1666158258.518353.1485858630674.JavaMail.zimbra@globaledgesoft.com>
Thats fine..
I am facing the problem with btgatt-server security options.
btgatt-server is not connecting to any clients even with btgatt-client when the security level of btgatt-server is set to "medium" or "high".
btagatt-server is working fine with the security level "low"
Regards
Mallikarjun Phulari
----- Original Message -----
From: "Maxime CHEVALLIER" <maxime.chevallier@smile.fr>
To: "Mallikarjun Phulari" <p.mallikarjun@globaledgesoft.com>
Cc: linux-bluetooth@vger.kernel.org
Sent: Tuesday, January 17, 2017 2:21:42 PM
Subject: Re: [PATCH 1/2] tools/btgatt-client: Fix set-security interactive command
Hi,
> Hi i am running heart-rate service using gatt-server.
> And i am using gatttool as client.
> gatt-server with default security level "low" is working fine.
> But when try different security levels "medium" and "high" with -s
> option, it is not connecting with the gatttool.
>
> What might be the problem??
The patch you linked applies to the btgatt-client tool, you seem to be
using gatttool.
When using gatttool, the option '-l' must be used to specify the
security level.
Note that gatttool will soon be marked as deprecated, you might want to
use btgatt-client instead.
> Thanks & Regards
> Mallikarjun Phulari
Regards,
Maxime
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Disclaimer:- The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. The views expressed in this E-mail message (including the enclosure/(s) or attachment/(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of GlobalEdge. Before opening any mail and attachments please check them for viruses .GlobalEdge does not accept any liability for virus infected mails.
prev parent reply other threads:[~2017-01-31 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 10:36 [PATCH 1/2] tools/btgatt-client: Fix set-security interactive command Maxime Chevallier
2016-12-22 10:36 ` [PATCH 2/2] tools/btgatt-client: Update set-security usage Maxime Chevallier
2016-12-28 9:14 ` [PATCH 1/2] tools/btgatt-client: Fix set-security interactive command Luiz Augusto von Dentz
2017-01-17 7:05 ` Mallikarjun Phulari
2017-01-17 8:51 ` Maxime CHEVALLIER
[not found] ` <1666158258.518353.1485858630674.JavaMail.zimbra@globaledgesoft.com>
2017-01-31 10:30 ` Mallikarjun Phulari [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=306265495.518366.1485858639832.JavaMail.zimbra@globaledgesoft.com \
--to=p.mallikarjun@globaledgesoft.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=maxime.chevallier@smile.fr \
/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).