Re: L2CAP: One failing connection hurts others?

Hello Marcel!

I just tested this rather old dongle:

hci0:   Type: USB
       BD Address: 00:06:AB:80:6F:5C ACL MTU: 377:10  SCO MTU: 16:0
       UP RUNNING PSCAN ISCAN
       RX bytes:64709 acl:1565 sco:0 events:1055 errors:0
       TX bytes:38780 acl:1236 sco:0 commands:297 errors:0
       Features: 0xff 0xfd 0x05 0x00 0x00 0x00 0x00 0x00
       Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
       Link policy: RSWITCH HOLD SNIFF PARK
       Link mode: SLAVE ACCEPT
       Name: 'BlueZ (0)'
       Class: 0x000100
       Service Classes: Unspecified
       Device Class: Computer, Uncategorized
       HCI Ver: 1.1 (0x1) HCI Rev: 0x2 LMP Ver: 1.1 (0x1) LMP Subver: 
0x1007
       Manufacturer: Broadcom Corporation (15)

Same problem. I tried the same dongle one year ago and it was not 
supported by BlueZ. Now it is. Thumbs up for that!

Marcel Holtmann schrieb:

> There are more than one timeouts in the BlueZ stack. Even the ACL
> disconnect timeout is different for the initiator and the acceptor of
> and ACL connection. Keep an eye on the HCI disconnect events on each of
> your devices and compare the timestamps.
>  
I set my timeouts by setting SO_RCVTIMEO and SO_SNDTIMEO on the L2CAP 
socket. But I think this is just the socket timeout. Is there a way to 
influence the internal timeouts of BlueZ (L2CAP, ACL)?

Regards
Stefan



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m