[jira] [Commented] (MYNEWT-358) The nrf51 cannot connect to directed advertisers when both devices use LL privacy

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MYNEWT-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417966#comment-15417966 ] 

ASF subversion and git services commented on MYNEWT-358:
--------------------------------------------------------

Commit 6a5c8ae64fa31bffbf1424ffcd6930a57892586b in incubator-mynewt-core's branch refs/heads/phyrx_no_mbuf from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6a5c8ae ]

MYNEWT-358: nrf51 cannot connect to directed advertisers w/privacy

In order to fix this issue I have added the local RPA to the resolving list and
modified the code so that the RPA timer is a true LL timer that will be used
to regenerate local RPAs at the specified timeout. This allows the local RPA
to be generated early and not during an IFS interval


> The nrf51 cannot connect to directed advertisers when both devices use LL privacy
> ---------------------------------------------------------------------------------
>
>                 Key: MYNEWT-358
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-358
>             Project: Mynewt
>          Issue Type: Bug
>          Components: Nimble
>    Affects Versions: v0_9_0
>            Reporter: William San Filippo
>            Assignee: William San Filippo
>             Fix For: v0_10_0
>
>
> The current nimble stack takes too long from the end of receiving a directed advertisement where both inita and adva are using resolvable private address and the initiator is using a resolvable private address. Basically, it takes too long resolve everything, schedule the slave and construct the connect request.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)