From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: Toshiba and BT (SuSE 9.2)
Date: Tue, 14 Dec 2004 12:09:10 +0100 [thread overview]
Message-ID: <1103022550.2143.151.camel@pegasus> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAosiAEZOtxUiHqgChZUVmh8KAAAAQAAAAlDHre6TS5Uy1TgCuirvwRgEAAAAA@t-online.de>
Hi Peter,
> ##>> What means this, espacially refused(111)?
> ##>
> ##>in most cases this is PIN or link key problem. Check with
> ##>"hcidump -x" to be sure.
>
> I give you the responses of hcidump -x and hcidump -a
no need for both in this case and -X combines them.
> Linux-Notebook:~ # hcidump -x
> HCIDump - HCI packet analyzer ver 1.11
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> 8F 01 00 CE 0B 00 18 CC 02 00 00 00 01
> > HCI Event: Command Status (0x0f) plen 4
> 00 01 05 04
> > HCI Event: Role Change (0x12) plen 8
> 00 8F 01 00 CE 0B 00 01
> > HCI Event: Connect Complete (0x03) plen 11
> 00 29 00 8F 01 00 CE 0B 00 01 00
> < ACL data: handle 0x0029 flags 0x02 dlen 12
> L2CAP(s): Connect req: psm 15 scid 0x0040
> < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> 29 00 0F 00
> > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
> 8F 01 00 CE 0B 00 01
> > HCI Event: Command Complete (0x0e) plen 6
> 01 0D 08 00 29 00
> > HCI Event: Number of Completed Packets (0x13) plen 5
> 01 29 00 01 00
> > HCI Event: Max Slots Change (0x1b) plen 3
> 29 00 05
> > ACL data: handle 0x0029 flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0f00 scid 0x0040 result 2 status 0
this means PSM not supported. Are you sure that your AP supports the PAN
profile? Maybe you wanna try dund.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-12-14 11:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 19:00 Toshiba and BT (SuSE 9.2) Peter K. Martin
2004-12-13 20:03 ` [Bluez-users] " Marcel Holtmann
2004-12-14 10:28 ` AW: " Peter K. Martin
2004-12-14 10:32 ` Marcel Holtmann
2004-12-14 10:59 ` AW: " Peter K. Martin
2004-12-14 11:09 ` Marcel Holtmann [this message]
2004-12-14 11:37 ` Peter K. Martin
2004-12-14 11:47 ` Marcel Holtmann
2004-12-14 13:39 ` AW: " Peter K. Martin
2004-12-15 10:46 ` Marcel Holtmann
2004-12-15 11:08 ` AW: " Peter K. Martin
2004-12-15 11:13 ` Marcel Holtmann
2004-12-15 12:37 ` AW: " Peter K. Martin
2004-12-15 13:44 ` Marcel Holtmann
2004-12-15 15:58 ` AW: " Peter K. Martin
2004-12-15 17:05 ` Peter K. Martin
2004-12-15 17:28 ` Marcel Holtmann
2004-12-16 10:49 ` AW: [Bluez-users] " Peter K. Martin
2004-12-16 11:09 ` Marcel Holtmann
2004-12-16 14:21 ` AW: " Peter K. Martin
2004-12-16 19:53 ` Marcel Holtmann
2004-12-17 10:04 ` AW: " Peter K. Martin
2004-12-17 14:47 ` Marcel Holtmann
2004-12-15 8:33 ` AW: [Bluez-users] " Peter K. Martin
2004-12-15 10: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=1103022550.2143.151.camel@pegasus \
--to=marcel@holtmann.org \
--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