* Can't Connect RFCOMM Socket. Too many links.
@ 2004-08-04 21:36 Ramon A Reveron
2004-08-04 23:16 ` [Bluez-users] " Marcel Holtmann
0 siblings, 1 reply; 4+ messages in thread
From: Ramon A Reveron @ 2004-08-04 21:36 UTC (permalink / raw)
To: marcel, bluez-users; +Cc: bluez-users
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Hello There,
I'm having some problems while connecting to a serial profile device. If I
connect to a device using:
rfcomm connect 0 "device address" 1
the connection works perfectly. If by some reason the device disconnects
(i.e. out of range), I need to wait around 50 seconds to reconnect to it
providing that it is back in range.
If i try before the 50 seconds have pass, I get this error: "Can't Connect
RFCOMM Socket. Too many links."
Is this a normal behavior?
Is there a way of connecting to the device as soon as it comes back in
range?
How can you specify a "Link Timeout" with BlueZ?
Thanks for your time and help!
Kernel: 2.4.19
BlueZ utils 2.3
Best Regards,
Ramon
[-- Attachment #2: Type: text/html, Size: 1333 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bluez-users] Re: Can't Connect RFCOMM Socket. Too many links.
2004-08-04 21:36 Can't Connect RFCOMM Socket. Too many links Ramon A Reveron
@ 2004-08-04 23:16 ` Marcel Holtmann
2004-08-05 15:39 ` Ramon A Reveron
0 siblings, 1 reply; 4+ messages in thread
From: Marcel Holtmann @ 2004-08-04 23:16 UTC (permalink / raw)
To: Ramon A Reveron; +Cc: BlueZ Mailing List
Hi Ramon,
> I'm having some problems while connecting to a serial profile device.
> If I connect to a device using:
>
> rfcomm connect 0 "device address" 1
>
> the connection works perfectly. If by some reason the device
> disconnects (i.e. out of range), I need to wait around 50 seconds to
> reconnect to it providing that it is back in range.
> If i try before the 50 seconds have pass, I get this error: "Can't
> Connect RFCOMM Socket. Too many links."
>
> Is this a normal behavior?
maybe this is a link manager problem. Run "hcidump -x" to show us the
disconnect and the reconnect. What is the output of "hciconfig -a"?
> Is there a way of connecting to the device as soon as it comes back in
> range?
Only if you start running an inquiry.
> How can you specify a "Link Timeout" with BlueZ?
Check the Bluetooth specification for the appropriate HCI command.
> Kernel: 2.4.19
> BlueZ utils 2.3
You should update to 2.4.19-mh18 and bluez-utils-2.9 ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bluez-users] Re: Can't Connect RFCOMM Socket. Too many links.
2004-08-04 23:16 ` [Bluez-users] " Marcel Holtmann
@ 2004-08-05 15:39 ` Ramon A Reveron
2004-08-05 20:38 ` Marcel Holtmann
0 siblings, 1 reply; 4+ messages in thread
From: Ramon A Reveron @ 2004-08-05 15:39 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: BlueZ Mailing List, bluez-users-admin
[-- Attachment #1.1: Type: text/plain, Size: 1888 bytes --]
Hi Marcel,
Here are the two files:
Thanks for your time.
Ramon
Marcel Holtmann <marcel@holtmann.org>
Sent by: bluez-users-admin@lists.sourceforge.net
08/04/2004 07:16 PM
To: Ramon A Reveron/Raleigh/IBM@IBMUS
cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Re: Can't Connect RFCOMM Socket. Too
many links.
Hi Ramon,
> I'm having some problems while connecting to a serial profile device.
> If I connect to a device using:
>
> rfcomm connect 0 "device address" 1
>
> the connection works perfectly. If by some reason the device
> disconnects (i.e. out of range), I need to wait around 50 seconds to
> reconnect to it providing that it is back in range.
> If i try before the 50 seconds have pass, I get this error: "Can't
> Connect RFCOMM Socket. Too many links."
>
> Is this a normal behavior?
maybe this is a link manager problem. Run "hcidump -x" to show us the
disconnect and the reconnect. What is the output of "hciconfig -a"?
> Is there a way of connecting to the device as soon as it comes back in
> range?
Only if you start running an inquiry.
> How can you specify a "Link Timeout" with BlueZ?
Check the Bluetooth specification for the appropriate HCI command.
> Kernel: 2.4.19
> BlueZ utils 2.3
You should update to 2.4.19-mh18 and bluez-utils-2.9 ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
[-- Attachment #1.2: Type: text/html, Size: 2964 bytes --]
[-- Attachment #2: hciconfig.info --]
[-- Type: application/octet-stream, Size: 571 bytes --]
hci0: Type: USB
BD Address: 00:10:C6:22:A2:73 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:745 acl:10 sco:0 events:38 errors:0
TX bytes:547 acl:9 sco:0 commands:21 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: '7054'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
[-- Attachment #3: hcidump.info --]
[-- Type: application/octet-stream, Size: 10099 bytes --]
HCIDump - HCI packet analyzer ver 1.5
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 00 18 CC 02 00 00 00 01
> HCI Event: Command Status(0x0f) plen 4
00 01 05 04
> HCI Event: Link Key Request(0x17) plen 6
C2 46 0A 96 A0 00
< HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
C2 46 0A 96 A0 00 F1 8C E9 B4 8D 78 65 FC 59 AD D1 99 E1 08
49 14
> HCI Event: Command Complete(0x0e) plen 10
01 0B 04 00 C2 46 0A 96 A0 00
> HCI Event: Connect Complete(0x03) plen 11
00 2A 00 C2 46 0A 96 A0 00 01 01
< ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
2A 00 0E 00
> HCI Event: Number of Completed Packets(0x13) plen 5
01 2A 00 01 00
> HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
C2 46 0A 96 A0 00 01
> HCI Event: Command Complete(0x0e) plen 6
01 0D 08 00 2A 00
> HCI Event: Max Slots Change(0x1b) plen 3
2A 00 05
> ACL data: handle 0x002a flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0040 result 1 status 2
> ACL data: handle 0x002a flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0040 result 0 status 0
< ACL data: handle 0x002a flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets(0x13) plen 5
01 2A 00 01 00
> ACL data: handle 0x002a flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> ACL data: handle 0x002a flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 1024
< ACL data: handle 0x002a flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0
> HCI Event: Number of Completed Packets(0x13) plen 5
01 2A 00 01 00
< ACL data: handle 0x002a flags 0x02 dlen 8
L2CAP(d): cid 0x41 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 2A 00 01 00
> ACL data: handle 0x002a flags 0x02 dlen 8
L2CAP(d): cid 0x40 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x002a flags 0x02 dlen 18
L2CAP(d): cid 0x41 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 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 2A 00 01 00
> ACL data: handle 0x002a flags 0x02 dlen 18
L2CAP(d): cid 0x40 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 frame_size 320 max_retrans 0 credits 0
< ACL data: handle 0x002a flags 0x02 dlen 8
L2CAP(d): cid 0x41 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets(0x13) plen 5
01 2A 00 01 00
> ACL data: handle 0x002a flags 0x02 dlen 8
L2CAP(d): cid 0x40 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(d): cid 0x41 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(d): cid 0x40 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets(0x13) plen 5
01 2A 00 01 00
< ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(d): cid 0x41 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets(0x13) plen 5
01 2A 00 01 00
> ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(d): cid 0x40 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 0x002a flags 0x02 dlen 9
L2CAP(d): cid 0x41 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86
21
> ACL data: handle 0x002a flags 0x02 dlen 9
L2CAP(d): cid 0x40 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c
05
> HCI Event: Number of Completed Packets(0x13) plen 5
01 2A 00 01 00
> HCI Event: Disconn Complete(0x05) plen 4
00 2A 00 08
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 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
09 00 00 C2 46 0A 96 A0 00 01 00
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 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
09 00 00 C2 46 0A 96 A0 00 01 00
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 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
09 00 00 C2 46 0A 96 A0 00 01 00
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 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
09 00 00 C2 46 0A 96 A0 00 01 00
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 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
09 00 00 C2 46 0A 96 A0 00 01 00
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 00 18 CC 02 00 00 00 01
> HCI Event: Command Status(0x0f) plen 4
00 01 05 04
> HCI Event: Link Key Request(0x17) plen 6
C2 46 0A 96 A0 00
< HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
C2 46 0A 96 A0 00 F1 8C E9 B4 8D 78 65 FC 59 AD D1 99 E1 08
49 14
> HCI Event: Command Complete(0x0e) plen 10
01 0B 04 00 C2 46 0A 96 A0 00
> HCI Event: Connect Complete(0x03) plen 11
00 29 00 C2 46 0A 96 A0 00 01 01
< 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 0E 00
> HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
C2 46 0A 96 A0 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 0x0040 scid 0x0040 result 1 status 2
> 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 0x40 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 0x40 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 0x40 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 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 18
L2CAP(d): cid 0x40 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 frame_size 320 max_retrans 0 credits 0
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x40 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> 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 0x40 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x40 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x40 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets(0x13) plen 5
01 29 00 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x40 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x40 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets(0x13) plen 5
01 29 00 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 9
L2CAP(d): cid 0x40 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86
21
> HCI Event: Number of Completed Packets(0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 9
L2CAP(d): cid 0x40 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c
05
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bluez-users] Re: Can't Connect RFCOMM Socket. Too many links.
2004-08-05 15:39 ` Ramon A Reveron
@ 2004-08-05 20:38 ` Marcel Holtmann
0 siblings, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2004-08-05 20:38 UTC (permalink / raw)
To: Ramon A Reveron; +Cc: BlueZ Mailing List
Hi Ramon,
> Here are the two files:
your second connection creation results in this:
< HCI Command: Create Connection(0x01|0x0005) plen 13
C2 46 0A 96 A0 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
09 00 00 C2 46 0A 96 A0 00 01 00
The error code 0x09 actually means: CONNECTION LIMIT EXCEEDED (0X09)
The Connection Limit Exceeded error code indicates that an
attempt to create another connection failed because the
controller is already at its limit of the number of connections
it can support. The number of connections a device can support
is implementation dependent.
Maybe this is a problem of your GPS unit, because the Bluetooth dongle
you are using is build id 0x33c and that is a HCI 16.14 firmware.
And I saw that you are using security mode 3 in one of your devices.
Disable it. Maybe this causes the trouble.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-08-05 20:38 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-04 21:36 Can't Connect RFCOMM Socket. Too many links Ramon A Reveron
2004-08-04 23:16 ` [Bluez-users] " Marcel Holtmann
2004-08-05 15:39 ` Ramon A Reveron
2004-08-05 20:38 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox