From: Marcel Holtmann <marcel@holtmann.org>
To: Burkhard Fischer <b.fi2@web.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluepin bash script with immediate pin response
Date: Wed, 21 Jan 2004 14:57:17 +0100 [thread overview]
Message-ID: <1074693437.7088.85.camel@pegasus> (raw)
In-Reply-To: <400E5E94.6030104@web.de>
Hi Burkhard,
> here some more informations and the attached hci dump
>
> /bin/bluepin:
>
> #!/bin/bash
> #sleep 1
> echo "PIN:6bkgLuRqDpSIYZgP"
>
> command:
>
> magito:/etc/bluetooth# ciptool connect 00:04:0E:84:06:CA
> Can't connect L2CAP socket: Connection refused
> HCI Event: Link Key Request(0x17) plen 6
CA 06 84 0E 04 00
< HCI Command: Link Key Request Negative Reply(0x01|0x000c) plen 6
CA 06 84 0E 04 00
> HCI Event: PIN Code Request(0x16) plen 6
CA 06 84 0E 04 00
> ACL data: handle 0x0000 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 4 status 0
< HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23
CA 06 84 0E 04 00 10 36 62 6B 67 4C 75 52 71 44 70 53 49 59
5A 67 50
> HCI Event: Disconn Complete(0x05) plen 4
00 00 00 13
the problem seems to be the AP itself, because l2cap_conn_rsp with
result code 4 means "Connection refused - no resources available". Try
to update the firmware of your AP.
Regards
Marcel
-------------------------------------------------------
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
prev parent reply other threads:[~2004-01-21 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 16:38 [Bluez-users] bluepin bash script with immediate pin response Burkhard Fischer
2004-01-21 1:24 ` Marcel Holtmann
2004-01-21 11:12 ` Burkhard Fischer
2004-01-21 13:57 ` Marcel Holtmann [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=1074693437.7088.85.camel@pegasus \
--to=marcel@holtmann.org \
--cc=b.fi2@web.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