Authentication failure

RE: Authentication failure

Hung Bui — Thu, 17 Dec 2015 12:59:13 GMT

Hi Giglesias,

I'm sorry that you experiencing issue with the sniffer. It's a known issue and we are trying to fix it. There is a workaround is to unplug and plug the sniffer dongle and test (usually take a few times before you can track the connection).

RE: Authentication failure

giglesias — Thu, 17 Dec 2015 10:06:10 GMT

Hi Hung Thanks for the response. Using the Nordic Sniffer all I can see are the advertising packets. I can connect and discover the known GAT services of the peripheral with the nRF Master Control Panel Android app. But when I sniff the communication all I see are advertising packets.

The peripheral I am trying to connect to is a Nordic rnf51 series device, but someone else wrote the code and I do not have access tit. There is also and iOS app that communicates with the peripheral but that source is closed to me as well.

If I simulate the peripheral on a nRf51 it works great.

If I could get the Nordic sniffer to capture more than just advertisement packets I could probably figure this out.

Any suggestions would be greatly appreciated.

RE: Authentication failure

Hung Bui — Wed, 16 Dec 2015 12:32:54 GMT

Hi Giglesias,

Could you tell a little bit more on the "peripheral-specific authentication protocol" ? [DM]: >> BLE_GAP_EVT_AUTH_STATUS with status 0x83 telling that :

BLE_GAP_SEC_STATUS_AUTH_REQ 0x83 /**< Authentication requirements not met. */

It seems like it's sent from the application from one side. Do you have any call like sec_params_reply(conn_handle, BLE_GAP_SEC_STATUS_AUTH_REQ, ...) in your code ?

It's not clear if you triggered the normal Bluetooth pairing or not. If you can provide a sniffer trace it's easier to determine what's wrong.