diff options
author | RafaĆ Gajda <rafal.gajda@silvair.com> | 2020-04-07 11:32:51 +0200 |
---|---|---|
committer | Brian Gix <brian.gix@intel.com> | 2020-04-08 10:08:31 -0700 |
commit | 60423fed392a9f454a696622ce6afab61a610bef (patch) | |
tree | c953c0fb9c0745c60d1641bc651d784bf27cf033 /test | |
parent | 5b294a56664a8c7088d1eea2bc089d812a515794 (diff) | |
download | bluez-60423fed392a9f454a696622ce6afab61a610bef.tar.gz |
mesh: Ignore beacons with IVU if IV already updated
When daemon receives beacon with IV=n+1, IVU=False it will
start sending messages with new IV and set sequence to 0.
However if daemon receives another beacon with IV=n+1, IVU=True it
will go back to sending messages with old IV=n (IVU set to True).
Because sequence number has been reset those messages will be dropped
by replay protection and node will lose communication.
Once IV is updated daemon should not go back to using the old value.
This patch adds beacon rejection if IV has already been updated.
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions