This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Info about new nRF5 SDK v17.1.0

Hello

new nRD5 SDK v17.1.0

Can you please help me to find more about:

1.
"- NRFFOSDK-13484: Added an option in the Peer Manager to decide that a connection will not be processed by this module."

and
"2. - NRFFOSDK-13616: Updated handling of bonding events to be more sceptical of failed bonding/encryption attempts, since they can be the sign of an attack."

Dimitris

Parents
  • Hi Dimitris

    I will check internally if we have some more information regarding these changes, and get back to you. 

    Best regards
    Torbjørn

  • Hi

    So if I get it right

    There is a new option in peer manager (NRFFOSDK-13484), Nordic announce it and do not let customers to use it. Don't you thing it is bit strange?

    I do need code from other users, but it is really useful to know how to exclude connections from handled by PM 

    Dimitris

  • Hi Dimitris

    Not sure what you mean, you are obviously free to use this feature if you want Slight smile

    The pm_conn_exclude(..) function is documented here (the same documentation that you can find in the header file). 

    DimitrisP said:
    I do need code from other users, but it is really useful to know how to exclude connections from handled by PM 

    Could you provide some more information on what you are trying to do?

    The reason this feature wasn't there before is that normal BLE applications don't need it. If you don't want to do pairing/bonding for particular connections you can always do that, the only difference with this feature is that it allows you to handle pairing/bonding manually for specific connections. 

    Normally people use the peer_manager to avoid having to implement all of this themselves. 

    Best regards
    Torbjørn

Reply
  • Hi Dimitris

    Not sure what you mean, you are obviously free to use this feature if you want Slight smile

    The pm_conn_exclude(..) function is documented here (the same documentation that you can find in the header file). 

    DimitrisP said:
    I do need code from other users, but it is really useful to know how to exclude connections from handled by PM 

    Could you provide some more information on what you are trying to do?

    The reason this feature wasn't there before is that normal BLE applications don't need it. If you don't want to do pairing/bonding for particular connections you can always do that, the only difference with this feature is that it allows you to handle pairing/bonding manually for specific connections. 

    Normally people use the peer_manager to avoid having to implement all of this themselves. 

    Best regards
    Torbjørn

Children
No Data
Related