Re: [Bluez-devel] Pairing fails with RFCOMM

[Marcel Holtmann <marcel@holtmann.org>]

Hi Nils,

> I think I found a small problem with rfcomm concerning pairing.
> The problem is that if you try to connect to a "new" device which
> requires pairing using rfcomm you will be queried for y pin on both
> sides. But it seems that a connect timeout in rfcomm is way too short
> for being able to input the pin.
> It happened to me while trying to connect to a Siemens S55 mobile.
> I did a "rfcomm bind" and then opened minicom on the port. After that
> the mobile requests the pin. But before you can even start to input the
> pin minicom exits with an error.
> If I start another connection first, like with multisync, the whole
> connection process waits until the pin has been entered on both sides.

there is a difference between "rfcomm bind ..." and "rfcomm conn ...",
because on the "bind" case the connection is established by the TTY part
of the RFCOMM layer. In the case of "connect" the socket is creating the
connection and MultiSync is using the socket. Please try to reproduce
this behaviour with only using the rfcomm program and cat instead of
minicom to trigger this behaviour. Please include the binary hcidump.

And the important thing, what kernel are you using?

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel