From: "Michael Ellis" <michael.f.ellis@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dbus-1.pc not found
Date: Tue, 8 Aug 2006 09:58:19 -0400 [thread overview]
Message-ID: <7b9ca310608080658h4e5e64c3i2e3448bc67fc5278@mail.gmail.com> (raw)
In-Reply-To: <7b9ca310608071818v5871bb19y2593b7a693ca4ab6@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2003 bytes --]
On 8/7/06, Michael Ellis <michael.f.ellis@gmail.com> wrote:
>
> Hi Marcel,
>
> Thanks! That did the trick and it installed without error.
>
> So, if I may be so bold as to ask a little more help :-), I now have a
> configuration that almost works. I can plug a DBT-120 dongle into the linux
>
>
More information:
Apologies for top posting previous reply. The following is output from
hcidump following the hcitool cc command
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:0C:84:00:16:51 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:0C:84:00:16:51
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
bdaddr 00:0C:84:00:16:51
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
status 0x00 bdaddr 00:0C:84:00:16:51
> HCI Event: PIN Code Request (0x16) plen 6
bdaddr 00:0C:84:00:16:51
< HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
bdaddr 00:0C:84:00:16:51
> HCI Event: Command Complete (0x0e) plen 10
PIN Code Request Negative Reply (0x01|0x000e) ncmd 1
status 0x00 bdaddr 00:0C:84:00:16:51
> HCI Event: Connect Complete (0x03) plen 11
status 0x06 handle 41 bdaddr 00:0C:84:00:16:51 type ACL encrypt 0x00
Error: PIN or Key Missing
So it looks like there's a problem with pin exchange. I'm not familiar
enough with hcidump to be sure which unit is complaining about the pin.
Both should be using 0000, for time being, and that pin worked with the
same dongle from a Windows laptop. My pin helper is a shell script that
simply contains:
#!/bin/sh
echo -n PIN:0000
I've tried various enabling and disable auth and encrypt and also tried
setting security to none. In the latter case, the connection attempt times
out.
Any suggestions appreciated.
Thanks,
Mike
[-- Attachment #1.2: Type: text/html, Size: 2722 bytes --]
[-- Attachment #2: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-08-08 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 21:27 [Bluez-users] dbus-1.pc not found Michael Ellis
2006-08-07 23:13 ` bees
2006-08-08 1:04 ` Marcel Holtmann
2006-08-08 1:18 ` Michael Ellis
2006-08-08 13:58 ` Michael Ellis [this message]
2006-08-08 14:31 ` Michael Ellis
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=7b9ca310608080658h4e5e64c3i2e3448bc67fc5278@mail.gmail.com \
--to=michael.f.ellis@gmail.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