-
Notifications
You must be signed in to change notification settings - Fork 7.4k
Bluetooth: Mesh: Friend node Adding another Friend Update #20746
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
Comments
+70516 ms +70532 ms +70532 ms +70532 ms +70532 ms +70547 ms +70547 ms +70563 ms +70563 ms +70766 ms +70766 ms +70782 ms +70782 ms +70782 ms +71078 ms +74078 ms +74094 ms +74094 ms +74094 ms +74094 ms +74110 ms +74110 ms +74125 ms +74125 ms +75141 ms +75438 ms +75438 ms +75438 ms +75438 ms +76453 ms +79016 ms |
Fixes: #20746 According MESH/NODE/FRND/FN/BV-20-C should add another Friend Update. Signed-off-by: Lingao Meng <[email protected]>
Two
friend update
message are required in theMESH/NODE/FRND/FN/BV-20-C [Adding another Friend Update – Friend Node]
, but I did not find such processing logic in the code. But it's strange that I noticed that I have passed the certification ?In the authentication process, it is required that the first
friend_update
message should be MD = 1,Only in this case
enqueue_update(frnd, 1);
I tracked the process:
enqueue_update(frnd, 1); <--- enqueue_friend_pdu;
However
enqueue_friend_pdu
will not be called at this stage.If I'm right, the problem is this function
bt_mesh_friend_sec_update
:zephyr/subsys/bluetooth/mesh/friend.c
Lines 193 to 210 in 3cc5bda
If the flag
[frnd->sec_update]
is true before we set it, it is obvious that the lastfriend_update
will be lost.The text was updated successfully, but these errors were encountered: