public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Achim Bohnet <ach@mpe.mpg.de>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] bug link_key: no connection after AP was once accessed with Win XP AVM tools
Date: Wed, 31 Mar 2004 01:34:14 +0200	[thread overview]
Message-ID: <200403310134.14280.ach@mpe.mpg.de> (raw)

Hi,
to explore my AVM AP-X I once used WinXP.  After rebooting into
linux.  ciptool was unable to connect to the AP.  Fix/hack was to
shutdown hcid, move /etc/bluetooth/link_key away and restart hcid.
(I'm proud of this wild guess that fixed it ;)
Then I got a pin prompt again and everything started working again.

With the 'unusable-after-winxp-usage' link_key file I get

# ciptool connect 00:04:0E:85:34:F3
Can't connect L2CAP socket: Connection timed out

# hcidump -x gives:
HCIDump - HCI packet analyzer ver 1.5
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection(0x01|0x0005) plen 13
  F3 34 85 0E 04 00 18 CC 02 00 00 00 01
> HCI Event: Command Status(0x0f) plen 4
  00 01 05 04
> HCI Event: Link Key Request(0x17) plen 6
  F3 34 85 0E 04 00
< HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
  F3 34 85 0E 04 00 EE 90 55 76 1E 90 F2 DB 52 22 16 F7 5E 15
  A7 F5
> HCI Event: Connect Complete(0x03) plen 11
  05 00 00 F3 34 85 0E 04 00 01 00

I use debian testing with 2.6.4 and
ii  bluez-hcidump              1.5-2                      Analyses Bluetooth HCI packets
ii  bluez-pan                  1.1rel-3                   Personal area networking for Bluetooth devices
ii  bluez-pin                  0.22-1                     Bluetooth PIN helper with D-BUS support
ii  bluez-sdp                  1.5-2                      BlueZ Bluetooth SDP daemon and tool
ii  bluez-utils                2.4-6                      Utilities for controlling Bluetooth devices

Here's hcid.conf

allee(0) ~ $ tcgrep -v '^(\s*#|$)' /etc/bluetooth/hcid.conf
options {
        autoinit yes;
        security auto;
        pairing multi;
        pin_helper /usr/bin/bluepin.ach;
}
device {
        name "%h-%d";
        class 0x100;
        iscan enable; pscan enable;
        lm accept;
        lp rswitch,hold,sniff,park;
        auth enable;
        encrypt enable;
}

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- reddy@lion.austin.ibm.com


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-03-30 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 23:34 Achim Bohnet [this message]
2004-03-31  9:31 ` [Bluez-users] bug link_key: no connection after AP was once accessed with Win XP AVM tools Marcel Holtmann
     [not found]   ` <200403312212.08249.ach@mpe.mpg.de>
2004-03-31 22:48     ` 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=200403310134.14280.ach@mpe.mpg.de \
    --to=ach@mpe.mpg.de \
    --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