Security procedure stopped by GATT client timeout

RE: Security procedure stopped by GATT client timeout

Daniela_A — Mon, 22 Aug 2022 14:08:04 GMT

Hello Kenneth,

I solved my issue using a different workaround. Thank you for you help anyways

RE: Security procedure stopped by GATT client timeout

Kenneth — Thu, 18 Aug 2022 14:23:46 GMT

Choose from the dropdown (no filter):

RE: Security procedure stopped by GATT client timeout

Daniela_A — Thu, 18 Aug 2022 13:13:43 GMT

Hello Kenneth,

Yes, that is what I am doing. I am applying the filter and my device is shown in the log (the picture that I posted). However, once the connection is established, I am no longer able to sniff the packages; they stop showing.

Thanks

RE: Security procedure stopped by GATT client timeout

Kenneth — Wed, 17 Aug 2022 21:14:57 GMT

[quote user="Daniela_A"]All the packages are the same (except for the package count and timestamp). They stop showing once the connection is established.[/quote]

Make sure to follow from the user guide: "This list shows nearby devices that are advertising. When you start sniffing, All advertising devices is selected. Choose a device from the list to sniff that specific device."

[quote user="Daniela_A"]I was wondering: Is there a way to know what ATT procedure was interrupted?[/quote]

The sniffer log should show this, it's one of these:
https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.2.0%2Fgroup___b_l_e___g_a_t_t_c___t_i_m_e_o_u_t___m_s_c.html

RE: Security procedure stopped by GATT client timeout

Daniela_A — Wed, 17 Aug 2022 20:46:21 GMT

Hello,

I was wondering: Is there a way to know what ATT procedure was interrupted?

Thanks

RE: Security procedure stopped by GATT client timeout

Daniela_A — Wed, 17 Aug 2022 20:31:00 GMT

Hello

This is what I captured with the sniffer. All the packages are the same (except for the package count and timestamp). They stop showing once the connection is established.

Regarding the GATT client timeout, from the experience that I have with this pulse oximeter, every time a connection happens, there's a NRF_BLE_GATT_EVT_DATA_LENGTH_UPDATED event. This is not happening once the device is connected using the whitelist. Could be this procedure the one that is not responding?

RE: Security procedure stopped by GATT client timeout

Kenneth — Wed, 17 Aug 2022 13:51:21 GMT

Are you able to provide an on-air sniffer log?
https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE/Download

Follow the documentation on how to install and run:
https://infocenter.nordicsemi.com/pdf/nRF_Sniffer_BLE_UG_v4.1.0.pdf

I do not see any obvious reason why pairing/bonding procedures should affect ATT procedures:
https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.2.0%2Fgroup___b_l_e___g_a_t_t_c___t_i_m_e_o_u_t___m_s_c.html

Kenneth

RE: Security procedure stopped by GATT client timeout

Daniela_A — Tue, 16 Aug 2022 16:20:14 GMT

In addition I would like to say that when the event PM_EVT_CONN_SEC_PARAMS_REQ happens, this is what I do:

    case PM_EVT_CONN_SEC_PARAMS_REQ:
        {
          PRINT_RAW("Secure parameters request\n");
            // Allow pairing request from an already bonded peer.
            pm_conn_sec_config_t conn_sec_config = {.allow_repairing = true};
            pm_conn_sec_config_reply(p_evt->conn_handle, &conn_sec_config);
        }break;