From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't connect RFCOMM socket:Resourcetemporarilyunavailable
Date: Fri, 24 Aug 2007 16:59:59 +0200 [thread overview]
Message-ID: <1187967599.15402.183.camel@violet> (raw)
In-Reply-To: <d5920d1e0708240747g7199080at71c3350b641563e1@mail.gmail.com>
Hi Hamid,
> Oups! sorry, here is the output then:
>
> [root@localhost ~]# hcidump -X -V
> HCI sniffer - Bluetooth packet analyzer ver 1.18
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr 00:0D:18:60:14:8E 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: Connect Complete (0x03) plen 11
> status 0x00 handle 12 bdaddr 00:0D:18:60:14:8E type ACL encrypt 0x00
> < ACL data: handle 12 flags 0x02 dlen 12
> L2CAP(s): Connect req: psm 3 scid 0x0040
> < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> handle 12 policy 0x0f
> Link policy: RSWITCH HOLD SNIFF PARK
> > HCI Event: Command Complete (0x0e) plen 6
> Write Link Policy Settings (0x02|0x000d) ncmd 1
> status 0x00 handle 12
> > HCI Event: Max Slots Change (0x1b) plen 3
> 0000: 0c 00 05 ...
> > ACL data: handle 12 flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0042 scid 0x0040 result 1 status 2
> Connection pending - Authorization pending
> > HCI Event: Number of Completed Packets (0x13) plen 5
> handle 12
> > HCI Event: PIN Code Request (0x16) plen 6
> bdaddr 00:0D:18:60:14:8E
> > ACL data: handle 12 flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0040 result 3 status 0
> Connection refused - security block
> > HCI Event: Disconn Complete (0x05) plen 4
> status 0x00 handle 12 reason 0x13
> Reason: Remote User Teminated Connection
you don't have hcid running and so no PIN code handling at. So you can't
access the device. As simple as that.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-24 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 6:07 [Bluez-users] Can't connect RFCOMM socket: Resource temporarilyunavailable jaspreet singh
2007-08-22 7:58 ` Hamid MENOUAR
2007-08-22 14:26 ` [Bluez-users] Can't connect RFCOMM socket: Resourcetemporarilyunavailable jaspreet singh
2007-08-22 14:56 ` Hamid MENOUAR
2007-08-22 15:55 ` [Bluez-users] Can't connect RFCOMM socket:Resourcetemporarilyunavailable jaspreet singh
2007-08-24 12:18 ` Marcel Holtmann
2007-08-24 14:06 ` Hamid MENOUAR
2007-08-24 14:27 ` Marcel Holtmann
2007-08-24 14:47 ` Hamid MENOUAR
2007-08-24 14:59 ` Marcel Holtmann [this message]
2007-08-24 15:09 ` Hamid MENOUAR
2007-09-05 10:47 ` [Bluez-users] Can't connect RFCOMM socket: Resource temporarilyunavailable Xamindar
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=1187967599.15402.183.camel@violet \
--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