missing Generic L2CAP payload after the SM pairing rsp

RE: missing Generic L2CAP payload after the SM pairing rsp

Kenneth — Wed, 07 Mar 2018 13:42:05 GMT

Is it the same using nordic sniffer?
https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer/(language)/eng-GB

RE: missing Generic L2CAP payload after the SM pairing rsp

Arepa — Tue, 27 Feb 2018 18:45:04 GMT

Hi Petter,

I apologize for the long delay to respond it.

I always receive a generic L2CAP payload empty/CRC after a SM pairing rsp, it does not matter If I comment out or not the nrf_crypto_ecc_public_key_from_raw() and nrf_crypto_ecdh_shared_secret_compute(). what could be a possible cause for that empty L2CAP payload ? I mimicked the multirole_lesc example

RE: missing Generic L2CAP payload after the SM pairing rsp

ta2 — Sat, 25 Nov 2017 06:32:20 GMT

I don't know if this will make a difference, but the "if(central = true)" in your BLE_GAP_EVT_CONNECTED clause looks like a typo.

RE: missing Generic L2CAP payload after the SM pairing rsp

Petter Myhre — Tue, 21 Nov 2017 12:49:47 GMT

"it "works" using my two nrf52 central and peripheral, but is unable to pair with numeric comparison when I am using nrf connect."

Are you saying it works if you don't use nRF Connect?

The generic L2CAP payload looks like packets that has an CRC error, I'm not sure what their content is. Do you get that every time?

Could you share your complete project and tell me how to reproduce this?

RE: missing Generic L2CAP payload after the SM pairing rsp

Arepa — Mon, 20 Nov 2017 21:35:02 GMT

I uploaded the complete sniffer trace since the connection is started until it central sends encrpypted data mimic_lesc_example.psd I capture it using the TI sniffer

RE: missing Generic L2CAP payload after the SM pairing rsp

Petter Myhre — Mon, 20 Nov 2017 19:36:23 GMT

Could you edit your question and upload the complete sniffer trace?

RE: missing Generic L2CAP payload after the SM pairing rsp

Arepa — Mon, 20 Nov 2017 18:48:44 GMT

an additional concern I have is: after call pm_conn_secure() on my central I always receive an empty Generic L2CAP payload after the SM pairing rsp. just like in the capture above

RE: missing Generic L2CAP payload after the SM pairing rsp

Arepa — Mon, 20 Nov 2017 18:38:24 GMT

Hi Petter, It is include on my UART handle sorry for not included it above.

void uart_handle(app_uart_evt_t * p_event ) 
{
		if (p_event->evt_type == APP_UART_DATA_READY)		// interruption UART RX
		{
			
			if (m_numneric_match_requested)
			{
		
				sd_ble_gap_auth_key_reply(m_num_comp_conn_handle, BLE_GAP_AUTH_KEY_TYPE_PASSKEY, NULL); /*4*/
				m_numneric_match_requested = false;
			}	
		}
}

When I receive the the "BLE_GAP_EVT_PASSKEY_DISPLAY" over UART I check m_numneric_match_requested to call sd_ble_gap_auth_key_reply(); it has few validation because I am experimenting with it to port the security to my application, it "works" using my two nrf52 central and peripheral, but is unable to pair with numeric comparison when I am using nrf connect. I am using actually the same code from the multirole example

RE: missing Generic L2CAP payload after the SM pairing rsp

Petter Myhre — Mon, 20 Nov 2017 16:00:16 GMT

I can't see that you are calling sd_ble_gap_auth_key_reply() anywhere in the included code?