mesh: Secure Beacon - IV_Index/Key Refresh re-write This is a major rewrite of Secure Network Beacon (SNB) handling that includes: * Seperating Key Refresh from IV_Index handling This is a clearer handling of the two features. Although both features are represented in SNB's, they run independantly. * Creating a Seperate IV_Index initialization and updating state distinct from the current values sent and received in SNBs. If a restart occured during an IV Update procedure (96 hours long) the IVU bit got lost, and Sequence number resetting was not done correctly. * Assuring that all Nodes handled by daemon receive each incoming beacon. SNB handling previously stopped after the first node successfuly handled it, although the SNB may be valid for many local nodes.

Diffstat

2 files changed, 131 insertions(+), 222 deletions(-)