public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-users] Can't connect RFCOMM socket
@ 2005-01-19 18:33 soraberri
  2005-01-19 20:38 ` Marcel Holtmann
  0 siblings, 1 reply; 5+ messages in thread
From: soraberri @ 2005-01-19 18:33 UTC (permalink / raw)
  To: bluez-users

Hi

First of all thanks again for your time, maybe this is another proof of 
my lack of basic knowledge, but I've trying a lot and can't get ride of 
this error (I know this error is in many mails arround the list, but I 
have not find the particular remedy for mine)

When I try:

  rfcomm connect rfcomm0 00:10:60:A5:8F:8A 5

I get:

Can't connect RFCOMM socket: Connection refused
___________

modules l2cap, rfcomm are already loaded.
I have not paired both devices before, I only worry about this when the 
pop-up PIN helper window claims for the PIN... but this time it doesn't 
happen ¿how should I pair before?

Regards,


This is the dump for the device running rfcomm connect:
______________________________________________________________
HCIDump - HCI packet analyzer ver 1.11
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
   8A 8F A5 60 10 00 18 CC 02 00 00 00 01
 > HCI Event: Command Status (0x0f) plen 4
   00 01 05 04
 > HCI Event: Connect Complete (0x03) plen 11
   00 29 00 8A 8F A5 60 10 00 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 12
     L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
   29 00 0F 00
 > HCI Event: Number of Completed Packets (0x13) plen 5
   01 29 00 01 00
 > HCI Event: Command Complete (0x0e) plen 6
   01 0D 08 00 29 00
 > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
   8A 8F A5 60 10 00 01
 > HCI Event: Max Slots Change (0x1b) plen 3
   29 00 05
 > ACL data: handle 0x0029 flags 0x02 dlen 16
     L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
     MTU 1024
 > HCI Event: Number of Completed Packets (0x13) plen 5
   01 29 00 01 00
 > ACL data: handle 0x0029 flags 0x02 dlen 14
     L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
 > ACL data: handle 0x0029 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
     MTU 1024
< ACL data: handle 0x0029 flags 0x02 dlen 14
     L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
 > HCI Event: Number of Completed Packets (0x13) plen 5
   01 29 00 01 00
 > HCI Event: Number of Completed Packets (0x13) plen 5
   01 29 00 01 00
 > ACL data: handle 0x0029 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x0029 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [psm 3]
       RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
       dlci 10 frame_type 0 credit_flow 15 pri 7 ack_timer 0
       frame_size 1019 max_retrans 0 credits 7
 > HCI Event: Number of Completed Packets (0x13) plen 5
   01 29 00 01 00
 > ACL data: handle 0x0029 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DM: cr 1 dlci 10 pf 1 ilen 0 fcs 0xa6
< ACL data: handle 0x0029 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 0x0029 flags 0x02 dlen 12
     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
 > HCI Event: Number of Completed Packets (0x13) plen 5
   01 29 00 01 00
 > HCI Event: Number of Completed Packets (0x13) plen 5
   01 29 00 01 00
 > ACL data: handle 0x0029 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
 > ACL data: handle 0x0029 flags 0x02 dlen 12
     L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
   29 00 13
 > HCI Event: Command Status (0x0f) plen 4
   00 01 06 04
 > HCI Event: Disconn Complete (0x05) plen 4
   00 29 00 16

__________________________________________________________

and this is the dump for the remote device
________________________________________________________
HCIDump - HCI packet analyzer ver 1.11
device: hci0 snap_len: 1028 filter: 0xffffffff

 > HCI Event: Connect Request (0x04) plen 10

  AA 96 A5 60 10 00 04 01 12 01
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
  AA 96 A5 60 10 00 01

 > HCI Event: Command Status (0x0f) plen 4

  00 01 09 04

 > HCI Event: Connect Complete (0x03) plen 11

  00 29 00 AA 96 A5 60 10 00 01 00
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
  29 00 0F 00

 > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7

  AA 96 A5 60 10 00 01

 > HCI Event: Command Complete (0x0e) plen 6

  01 0D 08 00 29 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 3 scid 0x0040
< ACL data: handle 0x0029 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0

 > HCI Event: Number of Completed Packets (0x13) plen 5

  01 29 00 01 00

 > ACL data: handle 0x0029 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
    MTU 1024
< ACL data: handle 0x0029 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
    MTU 1024

 > HCI Event: Number of Completed Packets (0x13) plen 5

  01 29 00 01 00

 > HCI Event: Number of Completed Packets (0x13) plen 5

  01 29 00 01 00

 > ACL data: handle 0x0029 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0

 > ACL data: handle 0x0029 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
< ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7

 > HCI Event: Number of Completed Packets (0x13) plen 5

  01 29 00 01 00

 > ACL data: handle 0x0029 flags 0x02 dlen 18

    L2CAP(d): cid 0x0040 len 14 [psm 3]
      RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
      dlci 10 frame_type 0 credit_flow 15 pri 7 ack_timer 0
      frame_size 1019 max_retrans 0 credits 7
< ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 10 pf 1 ilen 0 fcs 0xa6

 > HCI Event: Number of Completed Packets (0x13) plen 5

  01 29 00 01 00

 > ACL data: handle 0x0029 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7

 > ACL data: handle 0x0029 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 0x0029 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040

 > HCI Event: Number of Completed Packets (0x13) plen 5

  01 29 00 01 00

 > 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



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 5+ messages in thread
* Re: [Bluez-users] Can't connect RFCOMM socket: resource temporarily unavailable
@ 2005-01-28 19:19 Marcel Holtmann
  2005-01-31 16:36 ` [Bluez-users] Can't connect RFCOMM socket Filipa Duarte
  0 siblings, 1 reply; 5+ messages in thread
From: Marcel Holtmann @ 2005-01-28 19:19 UTC (permalink / raw)
  To: BlueZ Mailing List

Hi Filipa,

> I am have Linux 2.6.9 in my laptop and an Conceptronic
> CBT 100U USB adapter. I installed bluez-utils-2.14 and
> bluez-libs-2.14.
> 
> 'hciconfig -a' shows me my device and 'hcitool scan'
> show me the computer of a friend (a windows pc). I can
> do an 'l2ping' and an 'rfcomm bind' to this computer
> without any problem. 
> 
> The problems arrive when I try to do 'rfcomm connect'.
> The answer is: "Can't connect RFCOMM socket: resource
> temporarily unavailable". 

you can't use bind and connect together. Choose one.

> I saw on the web and on the mailling lists that there
> is a problem with the 'bluepin'. I checked mine and it
> didn't work. So, I created a new file (called pin in 
> /usr/bin/) with:
> 
> #!bin/sh
> # file: /usr/bin/pin
> echo -n "PIN: "
> cat /etc/bluetooth/pin
> 
> and created a file in /etc/bluetooth/ also called pin
> with a numerical the PIN code.
> 
> Still I could not make the 'rfcomm connect' work! It
> appears a window asking for the PIN in my friend's
> computer, but in my computer I still have the same
> answer.

Check with "hcidump -x" as root if it is really a PIN helper problem.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 5+ messages in thread
* [Bluez-users] Can't connect RFCOMM socket
@ 2008-03-19  6:45 Matt
  0 siblings, 0 replies; 5+ messages in thread
From: Matt @ 2008-03-19  6:45 UTC (permalink / raw)
  To: BlueZ users


[-- Attachment #1.1: Type: text/plain, Size: 1994 bytes --]

Hi,

                    I am using bluez-utils-3.28 and am trying to connect to
a Nokia phone from my PC which has a BT dongle.I run hcid .I scan for other
devies using hcitool scan..and connect to my Phone using....

$hcid &
$passkey-agent --default 0000 &
$ hcitool scan
$ rfcomm connect 0 00:0E:6D:E0:E5:13 1

The Phone asks for the pin . I enter "0000" as the PIN .After sometime I get
the error message
Can't connect RFCOMM socket: Resource temporarily unavailable.

hcidump shows that (After I enter the PIN on the phone )

> HCI Event: PIN Code Request (0x16) plen 6
< ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0064 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8
< ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0064 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0064 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
> ACL data: handle 1 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> ACL data: handle 1 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0064 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4

        I tried after removing the link keys
(/var/lib/bluetooth/XX:XX:XX:XX:XX:XX/) .Still I get the same error..What
could be the problem here..?
       When I try the same thing with a PC with Fedora Core5 (without the
latest bluez and passkey-agent), I am asked to enter the PIN when I enter it
on the phone and the connection is successful..

Thank you for your time and consideration,
regards,
Matt.

[-- Attachment #1.2: Type: text/html, Size: 2557 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2008-03-19  6:45 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-19 18:33 [Bluez-users] Can't connect RFCOMM socket soraberri
2005-01-19 20:38 ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2005-01-28 19:19 [Bluez-users] Can't connect RFCOMM socket: resource temporarily unavailable Marcel Holtmann
2005-01-31 16:36 ` [Bluez-users] Can't connect RFCOMM socket Filipa Duarte
2005-01-31 17:07   ` Marcel Holtmann
2008-03-19  6:45 Matt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox