From: Ruben Jenster <RJenster@web.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] authentication problem - link_key prevents from pairing
Date: Sun, 1 May 2005 22:10:59 +0200 [thread overview]
Message-ID: <200505012210.59716.RJenster@web.de> (raw)
In-Reply-To: <1114959364.21785.18.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
Hi,
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.
My bluetooth dongle is from allnet and is attached to the usb port of a
nforce2 mobo.
I allready submitted a bug report at the kde bugtracker cause I thought
this is a kdebluetooth problem. Please look at
http://bugs.kde.org/show_bug.cgi?id=104876 which could also be usefull
information.
I tried all versions of bluez-utils and bluez-libs from 2.7 till 2.16
and kdebluetooth from 20041107 till 0.99_beta1 in nearly every combination but
everytime the same problem.
Curious is that on my thinkpad (T41p) evertime I pair my headset with the
buildtin bluetooth module I'm asked for the PIN.
I'm really stumped. Please help me.
Regards
Ruben
[-- Attachment #2: hciconfig.info --]
[-- Type: text/plain, Size: 1277 bytes --]
Bluetooth Dongle Allnet 1575
hci0: Type: USB
BD Address: 00:0C:55:FD:8E:6B ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:708 acl:0 sco:0 events:25 errors:0
TX bytes:335 acl:0 sco:0 commands:23 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Thinkpad (0)'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
Thinkpad T41p internal bluetooth
hci0: Type: USB
BD Address: 00:20:E0:7D:21:C7 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:384 acl:0 sco:0 events:17 errors:0
TX bytes:309 acl:0 sco:0 commands:16 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Thinkpad (1)'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x222 LMP Ver: 1.1 (0x1) LMP Subver: 0x222
Manufacturer: Cambridge Silicon Radio (10)
next prev parent reply other threads:[~2005-05-01 20:10 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 ` Ruben Jenster [this message]
2005-05-01 23:19 ` [Bluez-devel] authentication problem - link_key prevents from pairing Marcel Holtmann
2005-05-02 11:27 ` Ruben Jenster
2005-05-02 12:05 ` Marcel Holtmann
2005-05-02 14:57 ` Ruben Jenster
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=200505012210.59716.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox