Re: [Bluez-devel] RFCOMM DISC dlci=0 missing after server closesocket?

Marcel Holtmann
2007-07-18T08:18:55Z

Hi Art,

> Our RFCOMM application conducts a brief session to validate the application on a
> partner device, then terminates the session and gives the user an option to
> reconnect to the partner application. When the local application uses the
> Microsoft stack or Toshiba stack on a WinXP, and the remote application uses
> BlueZ, the user-driven connect fails if issued less than 60 secs before the
> first session is disconnected.
>
> This appears to be a flaw in the BlueZ implementation, but I am no expert on the
> subject. Is my analysis correct? If it is, can someone suggest a workaround?
>
> The RFCOMM specification from Bluetooth 1.1 says
>
> << The device closing the last connection (DLC) on a particular session is
> responsible for closing the multiplexer by closing the corresponding L2CAP channel.

the Linux kernel 2.6.22 should behave according to the specification.

Regards

Marcel