From: Johan Hedberg <johan.hedberg@gmail.com>
To: Steffen Becker <steffen.becker@tu-ilmenau.de>
Cc: Gustavo Padovan <gustavo@padovan.org>, linux-bluetooth@vger.kernel.org
Subject: Re: Can't connect Bluetooth Devices
Date: Thu, 3 May 2012 12:44:29 +0300 [thread overview]
Message-ID: <20120503094429.GA6226@x220> (raw)
In-Reply-To: <4FA23B93.8090204@tu-ilmenau.de>
Hi Steffen,
On Thu, May 03, 2012, Steffen Becker wrote:
> >A linkkey is created during the pairing procedure, just pair your
> >devices and you will be done.
> >And let only bluetoothd touch the /var/lib/bluetooth
> >directory, don't touch there yourself.
> >
> > Gustavo
>
> Thanks for your fast reply, but that's exactly what I don't know:
> How can I pair my devices?
You pair using the CreatePairedDevice D-Bus method that BlueZ provides.
There are various front-ends that you can use to call this method. If
you've got GNOME installed then a pairing wizard should be just a few
mouse clicks away through the Bluetooth icon in the upper right-hand
corner. If you've only got the command line you can use e.g. the
simple-agent python script (under the test subdirectory):
test/simple-agent hci0 <remote address>
Btw, is there something that the network plugin (which you can operate
using e.g. test/test-network) doesn't provide but pand does? We'll
probably remove pand from the source tree along with BlueZ 5.0 so it'd
be good to know any deficiencies it has.
Johan
next prev parent reply other threads:[~2012-05-03 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 11:35 Can't connect Bluetooth Devices Steffen Becker
2012-04-24 20:57 ` Steffen Becker
2012-04-27 7:31 ` Steffen Becker
2012-05-02 22:54 ` Steffen Becker
2012-05-02 22:58 ` Gustavo Padovan
2012-05-03 8:02 ` Steffen Becker
2012-05-03 9:44 ` Johan Hedberg [this message]
2012-05-06 18:35 ` Steffen Becker
2012-05-09 12:05 ` Steffen Becker
2012-05-09 14:28 ` Steffen Becker
2012-05-14 22:23 ` Steffen Becker
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=20120503094429.GA6226@x220 \
--to=johan.hedberg@gmail.com \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=steffen.becker@tu-ilmenau.de \
/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).