missing Generic L2CAP payload after the SM pairing rsp

[Arepa]

I updated the original question

Hi, I am working with two nRF52 SDK13 central and peripheral, with no display, each is connected thought UART to a software interface, so I am mimicking the example multi role lesc,

I am able to pair, bond and encrypt the link, but I am wondering why I am getting a empty Generic L2CAP payload after the SM pairing rsp, it happens to each new connection when bonding, and if I am not bonding it happens always to each connection.

my sniffer capture:

The only difference between "my application" or multirole_lesc example mimic is. on my application, I am not performing a discovery service because I know where are all my handles for each characteristic and I connect only my own devices.

my code for the ble events realted to security

my scenario is pretty similar to this guy:what-is-the-reason-for-ble_gap_sec_status_dhkey_failure/

[Petter Myhre]

"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?

[Arepa]

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

[Kenneth]

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