All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruben Jenster <RJenster@web.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] authentication problem - link_key prevents from pairing
Date: Mon, 2 May 2005 16:57:45 +0200	[thread overview]
Message-ID: <200505021657.45204.RJenster@web.de> (raw)
In-Reply-To: <1115035517.21785.112.camel@pegasus>

On Monday 02 May 2005 14:05, Marcel Holtmann wrote:
> Hi Ruben,
>
> > > > I've a really enerving problem.
> > > >
> > > > On my desktop I'm not able to pair my headset without
> > > > deleting /etc/bluetooth/link_key. After deleting the link_key
> > > > the pinhelper pops up and asks for the pin. I insert them and
> > > > I'm able to connect.
> > >
> > > use the latest BlueZ utilities and run "hcidump -X -V" as root, so we
> > > can see what is going on.
> >
> > Ok, I've attached the hcidump output
> >
> > test sequence:
> > deleting link_key (if existent)
> > pair with  headset (btsco2 00:0D:B5:80:21:04 )
> > 	success -> successfull attempt (after having link_key deleted)
> > switching headset off
> > pair with  headset (btsco2 00:0D:B5:80:21:04 )
> > 	failure -> authentication problem (when not having link_key deleted)
>
> make sure that only _one_ hcid is running at a time and I don't know
> what else programs are you running, but all this RSSI etc. stuff that
> uses the handle 0 is wrong.

This problem even exists when I restart bluetooth services. i checked that
only one instance of hcid is running. 

>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

-- 
a bug a day keeps the boredom away

-- 
a bug a day keeps the boredom away


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-05-02 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01 13:38 [Bluez-devel] BlueZ: Accepting incoming traffic Joshua Davis
2005-05-01 13:51 ` Marcel Holtmann
2005-05-01 14:26   ` Joshua Davis
2005-05-01 14:56     ` Marcel Holtmann
2005-05-01 15:13       ` Joshua Davis
2005-05-01 15:23         ` Marcel Holtmann
2005-05-01 15:41           ` Joshua Davis
2005-05-01 15:48             ` Marcel Holtmann
2005-05-01 20:10       ` [Bluez-devel] authentication problem - link_key prevents from pairing Ruben Jenster
2005-05-01 23:19         ` Marcel Holtmann
2005-05-02 11:27           ` Ruben Jenster
2005-05-02 12:05             ` Marcel Holtmann
2005-05-02 14:57               ` Ruben Jenster [this message]

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=200505021657.45204.RJenster@web.de \
    --to=rjenster@web.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.