From: "Nosve" <nosve@libero.it>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Pairing to devices with bluez and widcomm with same adapter
Date: Thu, 22 Jan 2004 18:21:40 +0100 [thread overview]
Message-ID: <AGELIJDLJNOPFNMOHHIFEECJCAAA.nosve@libero.it> (raw)
Someone has managed how to pair with both stacks, with the same pc/adapter?
The problem seems to be the fact that when paired, the devices exchange a
link key
that bluez/hcid save in /etc/bluetooth/link_key.
When widcomm try to pair, it exchange another link_key, because it didn't
find
a key in his database, which is returned different with the one exchanged
from
bluez stack.
I'm wondering of it is possible to changhe the bdaddr of the bt adapter, so
the
remote device saves the keys for two different devices, but I didn't find
anything
for this 'solution'.
Another possibility may be the synchronization of the keys between the two
stacks,
but I don't know how to xtract them..
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-01-22 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 17:21 Nosve [this message]
2004-01-22 22:20 ` [Bluez-users] Pairing to devices with bluez and widcomm with same adapter Marcel Holtmann
2004-01-23 9:30 ` R: [Bluez-users] Pairing to devices with bluez and widcomm withsame adapter Nosve
2004-01-23 13:38 ` Marcel Holtmann
2004-01-23 15:58 ` R: [Bluez-users] Pairing to devices with bluez and widcommwithsame adapter Nosve
2004-01-23 16:15 ` Marcel Holtmann
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=AGELIJDLJNOPFNMOHHIFEECJCAAA.nosve@libero.it \
--to=nosve@libero.it \
--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