Hi Eiko, On Mon, Apr 06, 2009, Eiko Oltmanns wrote: > I think my code should be correct, isn't it? Is there maybe an option in the > kernel config, that could cause such a behaviour of the socket? Take a look at existing examples in the bluez source, e.g. tools/rctest.c. You're missing a call to bind after the call to socket and before the call to connect. Joah -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
