From: Russell Senior <seniorr@aracnet.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] connecting to a serial dongle with a PIN
Date: 26 Apr 2005 13:04:12 -0700 [thread overview]
Message-ID: <86oec12tkz.fsf@coulee.tdb.com> (raw)
Could someone please explain to me how I connect from a USB bluetooth
dongle to a bluetooth serial dongle that uses a PIN. I try this:
# l2ping 00:0B:CE:00:7A:8F
Can't connect: Permission denied
A simultaneous hcidump shows:
# hcidump -V
HCI sniffer - Bluetooth packet analyzer ver 1.17
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: PIN Code Request (0x16) plen 6
< HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
> HCI Event: Command Complete (0x0e) plen 10
PIN Code Request Negative Reply (0x01|0x000e) ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x18 handle 41 bdaddr 00:0B:CE:00:7A:8F type ACL encrypt 0x00
Error: Unknown LMP PDU
This is on a Debian/unstable system with:
bluez-hcidump 1.17-1
bluez-pin 0.25-1
bluez-utils 2.15-1
installed. Linux kernel v2.6.11.7.
Thanks!
--
Russell Senior ``I have nine fingers; you have ten.''
seniorr@aracnet.com
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-04-26 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 20:04 Russell Senior [this message]
2005-04-26 20:24 ` [Bluez-users] connecting to a serial dongle with a PIN 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=86oec12tkz.fsf@coulee.tdb.com \
--to=seniorr@aracnet.com \
--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