public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] can no longer connect with pand
Date: Thu, 09 Dec 2004 16:05:05 +0100	[thread overview]
Message-ID: <1102604706.9988.225.camel@pegasus> (raw)
In-Reply-To: <200412091557.33825.wim.delvaux@adaptiveplanet.com>

Hi Wim,

> Here is the hcidump -a output  To me it looks like the link_key (which should 
> exist since devices are paired) is still OK.  However connection fails
> 
> What might be wrong ?
> 
> device: hci0 snap_len: 1028 filter: 0xffffffff
> > HCI Event: Connect Request (0x04) plen 10
>   96 85 0D C7 02 00 12 01 12 01
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
>   96 85 0D C7 02 00 01
> > HCI Event: Command Status (0x0f) plen 4
>   00 01 09 04
> > HCI Event: Link Key Request (0x17) plen 6
>   96 85 0D C7 02 00
> < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
>   96 85 0D C7 02 00 83 82 FF 06 0B 83 05 4F 15 E0 05 C5 A0 1C
>   2A 30
> > HCI Event: Command Complete (0x0e) plen 10
>   01 0B 04 00 96 85 0D C7 02 00
> > HCI Event: Connect Complete (0x03) plen 11
>   00 29 00 96 85 0D C7 02 00 01 00
> < HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
>   29 00 18 CC
> > HCI Event: Max Slots Change (0x1b) plen 3
>   29 00 05
> > HCI Event: Command Status (0x0f) plen 4
>   00 01 0F 04
> > HCI Event: Connection Packet Type Changed (0x1d) plen 5
>   00 29 00 18 CC
> > ACL data: handle 0x0029 flags 0x02 dlen 12
>     L2CAP(s): Connect req: psm 15 scid 0x0040
> < ACL data: handle 0x0029 flags 0x02 dlen 16
>     L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0040 result 2 status 0
> > HCI Event: Number of Completed Packets (0x13) plen 5
>   01 29 00 01 00
> > HCI Event: Disconn Complete (0x05) plen 4
>   00 29 00 13
> > HCI Event: Connect Request (0x04) plen 10
>   96 85 0D C7 02 00 12 01 12 01
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
>   96 85 0D C7 02 00 01
> > HCI Event: Command Status (0x0f) plen 4
>   00 01 09 04
> > HCI Event: Link Key Request (0x17) plen 6
>   96 85 0D C7 02 00
> < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
>   96 85 0D C7 02 00 83 82 FF 06 0B 83 05 4F 15 E0 05 C5 A0 1C
>   2A 30
> > HCI Event: Command Complete (0x0e) plen 10
>   01 0B 04 00 96 85 0D C7 02 00
> > HCI Event: Connect Complete (0x03) plen 11
>   00 2A 00 96 85 0D C7 02 00 01 00
> < HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
>   2A 00 18 CC
> > HCI Event: Max Slots Change (0x1b) plen 3
>   2A 00 05
> > HCI Event: Command Status (0x0f) plen 4
>   00 01 0F 04
> > HCI Event: Connection Packet Type Changed (0x1d) plen 5
>   00 2A 00 18 CC
> > ACL data: handle 0x002a flags 0x02 dlen 12
>     L2CAP(s): Connect req: psm 15 scid 0x0040
> < ACL data: handle 0x002a flags 0x02 dlen 16
>     L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0040 result 2 status 0
> > HCI Event: Number of Completed Packets (0x13) plen 5
>   01 2A 00 01 00

the result 2 means connection refused, because the PSM is not supported
and this is mostly because no pand is running.

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

      reply	other threads:[~2004-12-09 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 14:57 [Bluez-users] can no longer connect with pand wim delvaux
2004-12-09 15:05 ` 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=1102604706.9988.225.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