From: "Harald Niederländer" <harald.niederlaender@ibmt.fraunhofer.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [Fwd: Re: Problem connecting Bluetooth device]
Date: Wed, 28 Jun 2006 13:29:37 +0200 [thread overview]
Message-ID: <44A26821.9030904@ibmt.fraunhofer.de> (raw)
In-Reply-To: <1151493008.26495.0.camel@localhost>
Hi Marcel,
Marcel Holtmann schrieb:
> Hi Harald,
>
>
>>>>The problem regarding the linkkey is that the stored linkkey from the first connection is
>>>>OK and all further connections are successful. But if I switch off and then switch on the
>>>>remote device, a new linkkey, different from the first, will be generated, but the old
>>>>linkkey will not be overwritten with the new one! Therefore I can contact the remote
>>>>device only one time (after entering the PIN). Why the linkkey is not overwritten?!
>>>
>>>
>>>how can the remote device generate a new link key when it is switched
>>>off.
>>
>>Naturally the device is switched on again. Then after entering the PIN, a new linkkey,
>>different from the first, will be generated. Maybe the linkkey is only temporary and for
>>each session a new linkkey will be genereted from a random number and the PIN.
>
>
> this is possible, but this doesn't explain why the stored link key on
> your device is different from the link key provided on the next connect.
The reason is, that the stored linkkey is the result from the first connection, and
because each new generated linkkey, after switch off and later switch on the device, is
different from the first linkkey and the old linkkey will not be overwritten.
Regards
Harald
> This is what we saw in the hcidump.
>
> Regards
>
> Marcel
>
>
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-28 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4497CE54.5080305@ibmt.fraunhofer.de>
2006-06-21 6:46 ` [Bluez-devel] [Fwd: Re: Problem connecting Bluetooth device] Harald Niederländer
2006-06-21 9:45 ` Marcel Holtmann
2006-06-21 10:22 ` Harald Niederländer
2006-06-21 10:38 ` Marcel Holtmann
2006-06-21 11:22 ` Harald Niederländer
2006-06-22 15:32 ` yang.guangxiang
2006-06-27 13:33 ` Harald Niederländer
2006-06-27 13:55 ` Wagner Bezerra
2006-06-28 6:02 ` Harald Niederländer
2006-06-28 7:32 ` Marcel Holtmann
2006-06-28 10:51 ` Harald Niederländer
2006-06-28 11:10 ` Marcel Holtmann
2006-06-28 11:29 ` Harald Niederländer [this message]
2006-06-28 11:37 ` 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=44A26821.9030904@ibmt.fraunhofer.de \
--to=harald.niederlaender@ibmt.fraunhofer.de \
--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).