|
[Zephyr-users] #BluetoothMesh guest key implementation
#bluetoothmesh
Hi Vikrant, It's more of a provisioner issue than a Zephyr issue. On the Zephyr side all you need to do is make sure your configuration allows at least two network keys. Then you need to make your pro
Hi Vikrant, It's more of a provisioner issue than a Zephyr issue. On the Zephyr side all you need to do is make sure your configuration allows at least two network keys. Then you need to make your pro
|
By
Johan Hedberg
·
|
|
#BluetoothMesh guest key implementation
#bluetoothmesh
Hi, https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-faq As per this link, under the heading of #VisitorAttacks we could see : "Visitor attacks are prevented by giving gues
Hi, https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-faq As per this link, under the heading of #VisitorAttacks we could see : "Visitor attacks are prevented by giving gues
|
By
...
·
|
|
#BluetoothMesh URI provisioning 2 messages
#bluetoothmesh
Hi Vikrant, This is already supported using the "const char *uri" member of struct bt_mesh_prov. Johan
Hi Vikrant, This is already supported using the "const char *uri" member of struct bt_mesh_prov. Johan
|
By
Johan Hedberg
·
|
|
What is need of addition authentication in case of #BluetoothMesh if ECDH public key exchanged over OOB ?
#bluetoothmesh
Hi, If #BluetoothMesh DEVICE ECDH-public key (oob public key) is exchanged over OOB channel then what is further need of authentication using input-OOB or output-OOB or static-OOB ? Thanks,
Hi, If #BluetoothMesh DEVICE ECDH-public key (oob public key) is exchanged over OOB channel then what is further need of authentication using input-OOB or output-OOB or static-OOB ? Thanks,
|
By
...
·
|
|
Data channels as ADV channel in #BluetoothMesh ? 5 messages
#bluetoothmesh
Except that this is not an error 😊 Mesh 1.0 is..... version 1.0. So let’s see what improvements come in future releases. Proprietary extensions are not a good idea though, no matter how tempting.
Except that this is not an error 😊 Mesh 1.0 is..... version 1.0. So let’s see what improvements come in future releases. Proprietary extensions are not a good idea though, no matter how tempting.
|
By
...
·
|
|
Concern about #BluetoothMesh Sequence number 3 messages
#bluetoothmesh
Hi Johan, Thanks for clarification & providing other additional important details. I think, Local sequence no. (for sender) & RPL (for receiver ) both are same for flash in terms of write cycle. Ultim
Hi Johan, Thanks for clarification & providing other additional important details. I think, Local sequence no. (for sender) & RPL (for receiver ) both are same for flash in terms of write cycle. Ultim
|
By
...
·
|
|
[ #BluetoothMesh ] possible Bug .. without assigning subscription address to Model, it is reacting to subscription address assign to other Model
#bluetoothmesh
This is observation based on following configuration done by #meshctl. Two nRF52840-PDK boards has been used for it. For Board 1. after provisioning, I used following commands to configure it ********
This is observation based on following configuration done by #meshctl. Two nRF52840-PDK boards has been used for it. For Board 1. after provisioning, I used following commands to configure it ********
|
By
...
·
|
|
SFCB to save persistence data for
#bluetoothmesh
Hi Johan, Is SFCB better option than NFFS to save #BluetoothMesh's persistence data ? Will it help us in case of nRF51 series which has limited flash storage ? Thank You !! ---------- Forwarded messag
Hi Johan, Is SFCB better option than NFFS to save #BluetoothMesh's persistence data ? Will it help us in case of nRF51 series which has limited flash storage ? Thank You !! ---------- Forwarded messag
|
By
...
·
|
|
Saving #BluetoothMesh Provisioning & Configuration related data on flash of nRF52 using NFFS 3 messages
#bluetoothmesh
As per this document .... nrf5_SDK_for_Mesh_v1.0.1_src/doc/introduction/mesh_hw_resources.md (I've attached this file for reference......very informative) The mesh stack uses flash to store the follow
As per this document .... nrf5_SDK_for_Mesh_v1.0.1_src/doc/introduction/mesh_hw_resources.md (I've attached this file for reference......very informative) The mesh stack uses flash to store the follow
|
By
...
·
|
|
understanding of #BluetoothMesh OOB authentication procedure 7 messages
#bluetoothmesh
Hi Vikrant, I answered this already here: https://lists.zephyrproject.org/pipermail/zephyr-devel/2018-January/008734.html I'm sure we'll eventually have proper support for it, but if you want to get i
Hi Vikrant, I answered this already here: https://lists.zephyrproject.org/pipermail/zephyr-devel/2018-January/008734.html I'm sure we'll eventually have proper support for it, but if you want to get i
|
By
Johan Hedberg
·
|
|
#BluetoothMesh self provisioning & configuration for Generic Models for testing
#bluetoothmesh
Hello World !! ----------------------------------------------------------------------------------------------------------------------------- { "$schema":"file:\/\/\/BlueZ\/Mesh\/schema\/mesh.jsonschem
Hello World !! ----------------------------------------------------------------------------------------------------------------------------- { "$schema":"file:\/\/\/BlueZ\/Mesh\/schema\/mesh.jsonschem
|
By
...
·
|
|
distance provisioning & configuration of #BluetoothMesh DEVICEs using single GATT-Proxy NODE
#bluetoothmesh
Hello, Currently I have been doing provisioning of #BluetoothMesh DEVICEs using #meshctl utility. But I've to individually makes connection with each device over PB-GATT for provisining & configuratio
Hello, Currently I have been doing provisioning of #BluetoothMesh DEVICEs using #meshctl utility. But I've to individually makes connection with each device over PB-GATT for provisining & configuratio
|
By
...
·
|