From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Newbie needs help to start
Date: Tue, 22 Jan 2008 12:13:00 -0200 [thread overview]
Message-ID: <4795F9EC.20509@aircable.net> (raw)
In-Reply-To: <QiqzmGYI.1201010734.9272710.fma@alezan.org>
> Ok, I got it. But how and where do I generate link keys?
>
You don't after the PIN transaction has completed successfully the
stacks handle the link generation. Links are stored under
/var/lib/bluetooth/<hci address>/linkkeys take into account that if you
switch from windows into linux, or if you plug your bluetooth dongle to
another pc, you will need to remove the linkkey from the file or it will
never work. It's like when RSA keys changes for a server.
> 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 ?
>
Exactly.
> If I understand correctly, rfcomm is not supported anymore? If it is the
> old way, what is the new way?
>
rfcomm as a tool isn't supported any more, rfcomm as technology is and
is the base for most of the bluetooth services. The new way is using the
dbus serial service. Which will also generate the rfcomm node, in a more
simple way, but if your distro is not well configured, it can be a
headhacke to get it to work.
> 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/
>
You WANT to get deep into bluez dbus api, not into the old hci lib api ;).
> I attached it.
>
Where? I don't think this list can take attached files.
-------------------------------------------------------------------------
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:13 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
2008-01-22 14:13 ` Manuel Naranjo [this message]
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=4795F9EC.20509@aircable.net \
--to=manuel@aircable.net \
--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