From: Burkhard Fischer <b.fi2@web.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] bluepin bash script with immediate pin response
Date: Tue, 20 Jan 2004 17:38:51 +0100 [thread overview]
Message-ID: <400D599B.3070004@web.de> (raw)
Hello,
I am using BlueFRITZ! USB Bluetooth dongle, the BlueFRITZ
AP-ISDN and ciptool for establishing a connection.
I want to replace the python script bluepin with a simple shell script
to avoid interactive authentication. A simple echo should do this,
however I found out that a connection is only established when the
bluepin bash script doesn't answer immediately.
Here is the syslog:
Jan 20 16:59:02 magito hcid[544]: pin_code_request
(sba=00:04:0E:82:F9:74, dba=00:04:0E:84:06:CA)
Jan 20 16:59:02 magito hcid[1088]: hci_send_cmd 6bkgLuRqDpSIYZgP
Jan 20 16:59:02 magito hcid[544]: pin_code_request
(sba=00:04:0E:82:F9:74, dba=00:04:0E:84:06:CA)
Jan 20 16:59:02 magito hcid[1091]: hci_send_cmd 6bkgLuRqDpSIYZgP
Jan 20 16:59:34 magito kernel: hci_cmd_task: hci0 command tx timeout
and with "sleep 1" before echoing the pin everything goes well (besides
the occasional tx timeout):
Jan 20 17:14:35 magito hcid[544]: pin_code_request
(sba=00:04:0E:82:F9:74, dba=0
0:04:0E:84:06:CA)
Jan 20 17:14:36 magito hcid[1577]: hci_send_cmd 6bkgLuRqDpSIYZgP
Jan 20 17:14:38 magito kernel: hci_cmd_task: hci0 command tx timeout
Jan 20 17:15:10 magito hcid[544]: pin_code_request
(sba=00:04:0E:82:F9:74, dba=0
0:04:0E:84:06:CA)
Jan 20 17:15:11 magito hcid[1596]: hci_send_cmd 6bkgLuRqDpSIYZgP
Jan 20 17:15:11 magito hcid[544]: pin_code_request
(sba=00:04:0E:82:F9:74, dba=0
0:04:0E:84:06:CA)
Jan 20 17:15:12 magito kernel: hci_cmd_task: hci0 command tx timeout
Jan 20 17:15:12 magito hcid[1602]: hci_send_cmd 6bkgLuRqDpSIYZgP
Jan 20 17:15:12 magito hcid[544]: link_key_notify (sba=00:04:0E:82:F9:74)
Jan 20 17:15:12 magito hcid[544]: Saving link key 00:04:0E:82:F9:74
00:04:0E:84:
06:CA
Jan 20 17:15:12 magito hcid[544]: link_key_notify (sba=00:04:0E:82:F9:74)
Jan 20 17:15:12 magito hcid[544]: Replacing link key 00:04:0E:82:F9:74
00:04:0E:
84:06:CA
Jan 20 17:15:12 magito kernel: Found 1 CAPI controller(s) on device
00:04:0E:84:
06:CA
Jan 20 17:15:12 magito kernel: kcapi: Controller 1: 00:04:0E:84:06:CA
attached
Jan 20 17:15:12 magito kernel: kcapi: card 1 "00:04:0E:84:06:CA" ready.
Jan 20 17:15:12 magito kernel: kcapi: notify up contr 1
Jan 20 17:15:12 magito kernel: capi: controller 1 up
I am using 2.4.24 kernel with the mh1-Patch and the source
bluez-libs-2.5.tar.gz
bluez-utils-2.4.tar.gz
bluez-sdp-1.5.tar.gz
Is there a reason for this behavior
thanks
Burkhard
-------------------------------------------------------
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
next reply other threads:[~2004-01-20 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 16:38 Burkhard Fischer [this message]
2004-01-21 1:24 ` [Bluez-users] bluepin bash script with immediate pin response Marcel Holtmann
2004-01-21 11:12 ` Burkhard Fischer
2004-01-21 13:57 ` 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=400D599B.3070004@web.de \
--to=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 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.