Tobias Jakobi wrote: > Anderson Lizardo wrote: >> I misunderstood the first output, it was actually the "info" command >> for the server from the client side. I thought it was the "show" >> command on the server side. That explains the missing "Powered" >> property :) >> > I see. Any idea how to isolate where the NotAvailable error origins from? > > With best wishes, > Tobias > > -- > 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 > Just a small note that I updated the bluez stacks (both on the server and the client) to 5.17. However the issue remains. I've also created log from the debug output of bluetoothd on both sides: http://www.math.uni-bielefeld.de/~tjakobi/bt-client.log http://www.math.uni-bielefeld.de/~tjakobi/bt-server.log Has anyone here actually managed to get a working TCP/IP network with recent bluez stack? Greets, Tobias -- 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
