From: Frédéric <fma@gbiloba.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Newbie needs help to start
Date: Tue, 22 Jan 2008 15:05:34 +0100 (CET) [thread overview]
Message-ID: <QiqzmGYI.1201010734.9272710.fma@alezan.org> (raw)
In-Reply-To: <4795F1C9.9050609@aircable.net>
Le 22/1/2008, "Manuel Naranjo" <manuel@aircable.net> a =E9crit:
>The process is simple, when you start a connection there's an initial
>phase where both devices authenticate, for this they exchange something
>called link key it's something similar to the way ssh works. If the link
>keys aren't generated yet then they exchange a PIN code, this is what
>the passkey agent does.
>
>After the authentication has been done then the connection is possible.
Ok, I got it. But how and where do I generate link keys?
>The fast and easy way to do it, it's using the old rfcomm tool from the
>bluez-utils package then you do:
>rfcomm connect rfcomm# ADDR [CHANNEL]
>
>For SPP you generally use channel 1 (the Serial3 is one of those cases)
>
># is a number of a valid and available rfcomm node, you will need to
>create it, check the web for the mayor number of the rfcomm node.
So, after I connect the BT device to the rfcomm channel, I can read/write
to it using the /dev/rfcomm entry, like if I'm using a /dev/ttySxx ?
If I understand correctly, rfcomm is not supported anymore? If it is the
old way, what is the new way?
>Again BlueZ is the stack, without it you can't do any bluetooth work
>under linux. D-Bus layer is used to make the programmers life easier as
>it hides all the bluez lib complexity (trust me you don't want to get
>much deeply into it, it requires serious bluetooth understanding)
I certainly don't want to deep inside d-bus, but the fact is that python
examples on bluez wiki use d-bus module :o/
>Anyway, and again, without a full hcidump trace, we can't tell you
>what's wrong, and guide you through this stuff.
I attached it.
>PS: BTW slackware has some patches in common with debian, they have a
>folder called /etc/bluetooth/passkeys there you can store files for
>default passkeys, you can have one called default and it uses for a
>default pin code, not the most secure way, but it works some how.
Ok.
--
Fr=E9d=E9ric
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-01-22 14:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 19:20 [Bluez-users] Newbie needs help to start Frédéric
2008-01-22 12:08 ` Frédéric
2008-01-22 12:38 ` Manuel Naranjo
2008-01-22 13:00 ` Frédéric
2008-01-22 13:38 ` Manuel Naranjo
2008-01-22 14:05 ` Frédéric [this message]
2008-01-22 14:13 ` Manuel Naranjo
2008-01-22 14:40 ` Frédéric
2008-01-22 14:42 ` Frédéric
2008-01-22 14:43 ` Miguel
2008-01-22 14:48 ` Manuel Naranjo
2008-01-22 14:56 ` Miguel
2008-01-22 15:02 ` Manuel Naranjo
2008-01-22 14:59 ` Frédéric
2008-01-22 15:04 ` Miguel
2008-01-22 15:31 ` Frédéric
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=QiqzmGYI.1201010734.9272710.fma@alezan.org \
--to=fma@gbiloba.org \
--cc=bluez-users@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