New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BLE Mesh When IV Update Procedure #17977
Labels
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Comments
jhedberg
added a commit
to jhedberg/zephyr
that referenced
this issue
Aug 14, 2019
The Mesh Profile Specification states in section 3.10.5 IV Update procedure: "The IV Update procedure is initiated by any node that is a member of a primary subnet", meaning if we're not on the primary subnet we should not try to initiate the procedure. Additionally this fixes initiating IV Update in all cases where the sequence is updated, by putting the code into bt_mesh_next_seq(). Fixes zephyrproject-rtos#17977 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
jhedberg
added a commit
that referenced
this issue
Aug 14, 2019
The Mesh Profile Specification states in section 3.10.5 IV Update procedure: "The IV Update procedure is initiated by any node that is a member of a primary subnet", meaning if we're not on the primary subnet we should not try to initiate the procedure. Additionally this fixes initiating IV Update in all cases where the sequence is updated, by putting the code into bt_mesh_next_seq(). Fixes #17977 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
jhedberg
added a commit
to joerchan/zephyr
that referenced
this issue
Aug 15, 2019
The Mesh Profile Specification states in section 3.10.5 IV Update procedure: "The IV Update procedure is initiated by any node that is a member of a primary subnet", meaning if we're not on the primary subnet we should not try to initiate the procedure. Additionally this fixes initiating IV Update in all cases where the sequence is updated, by putting the code into bt_mesh_next_seq(). Fixes zephyrproject-rtos#17977 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
nashif
pushed a commit
that referenced
this issue
Aug 15, 2019
The Mesh Profile Specification states in section 3.10.5 IV Update procedure: "The IV Update procedure is initiated by any node that is a member of a primary subnet", meaning if we're not on the primary subnet we should not try to initiate the procedure. Additionally this fixes initiating IV Update in all cases where the sequence is updated, by putting the code into bt_mesh_next_seq(). Fixes #17977 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
LeiW000
pushed a commit
to LeiW000/zephyr
that referenced
this issue
Sep 2, 2019
The Mesh Profile Specification states in section 3.10.5 IV Update procedure: "The IV Update procedure is initiated by any node that is a member of a primary subnet", meaning if we're not on the primary subnet we should not try to initiate the procedure. Additionally this fixes initiating IV Update in all cases where the sequence is updated, by putting the code into bt_mesh_next_seq(). Fixes zephyrproject-rtos#17977 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
According to the specification, IV update procedure
only
be initiated by any node is a member of the primary network, but it is not checked in the code.zephyr/subsys/bluetooth/mesh/net.c
Lines 728 to 782 in 9336e3e
zephyr/subsys/bluetooth/mesh/beacon.c
Lines 374 to 382 in 9336e3e
The text was updated successfully, but these errors were encountered: