From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Authentication failure
Date: Tue, 22 Nov 2005 12:07:04 +0100 [thread overview]
Message-ID: <1132657624.28644.5.camel@blade> (raw)
In-Reply-To: <7.0.0.10.0.20051121130729.0122d150@impulsesoft.com>
Hi Pragya,
> I have enabled authentication on BlueZ and I try to issue connection
> from another bluetooth device. I am seeing random behaviour with
> respect to authentication. Sometimes the authentication procedure
> goes through and a file "link_key" is created in /etc/bluetooth/.
>
> But most of the times, I see a link key request and no response from BlueZ.
> I am attaching the hcid.conf being used by me and also some logs (see
> below) collected using hcidump.
when using hcidump then use it with -X -V and as root. Nobody wants to
decode the HCI commands and events by themself.
If the link key requests are not answered, I suspect that hcid is not
running. If it runs make sure only one instance is running.
At some point we moved the link key storage to /var/lib/bluetooth and it
is also a text file now.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-11-22 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 7:44 [Bluez-devel] Authentication failure Pragya Gupta
2005-11-22 11:07 ` Marcel Holtmann [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=1132657624.28644.5.camel@blade \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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).