Searched refs:subnets (Results 1 – 10 of 10) sorted by relevance
/Zephyr-latest/subsys/bluetooth/mesh/ |
D | subnet.c | 62 static struct bt_mesh_subnet subnets[CONFIG_BT_MESH_SUBNET_COUNT] = { variable 268 for (int i = 0; i < ARRAY_SIZE(subnets); i++) { in subnet_alloc() 270 if (subnets[i].net_idx == net_idx) { in subnet_alloc() 271 return &subnets[i]; in subnet_alloc() 274 if (!sub && subnets[i].net_idx == BT_MESH_KEY_UNUSED) { in subnet_alloc() 275 sub = &subnets[i]; in subnet_alloc() 587 for (int i = 0; i < ARRAY_SIZE(subnets); i++) { in bt_mesh_subnet_node_id_set() 588 if (subnets[i].net_idx != BT_MESH_KEY_UNUSED && in bt_mesh_subnet_node_id_set() 589 subnets[i].node_id == BT_MESH_FEATURE_ENABLED && in bt_mesh_subnet_node_id_set() 590 subnets[i].priv_beacon_ctx.node_id) { in bt_mesh_subnet_node_id_set() [all …]
|
D | cdb.c | 90 .subnets = { 775 for (i = 0; i < ARRAY_SIZE(bt_mesh_cdb.subnets); ++i) { in bt_mesh_cdb_clear() 776 if (bt_mesh_cdb.subnets[i].net_idx != BT_MESH_KEY_UNUSED) { in bt_mesh_cdb_clear() 777 bt_mesh_cdb_subnet_del(&bt_mesh_cdb.subnets[i], true); in bt_mesh_cdb_clear() 821 for (i = 0; i < ARRAY_SIZE(bt_mesh_cdb.subnets); ++i) { in bt_mesh_cdb_subnet_alloc() 822 sub = &bt_mesh_cdb.subnets[i]; in bt_mesh_cdb_subnet_alloc() 854 for (i = 0; i < ARRAY_SIZE(bt_mesh_cdb.subnets); ++i) { in bt_mesh_cdb_subnet_get() 855 if (bt_mesh_cdb.subnets[i].net_idx == net_idx) { in bt_mesh_cdb_subnet_get() 856 return &bt_mesh_cdb.subnets[i]; in bt_mesh_cdb_subnet_get()
|
D | Kconfig | 385 int "Maximum number of subnets in the database" 389 This option specifies how many subnets that can at most be 1796 int "Maximum number of mesh subnets per network" 1800 This option specifies how many subnets a Mesh network can
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | brg_cfg.rst | 8 This feature allows mesh networks to use subnets for area isolation, but to also allow communication 9 between specific devices in different, adjacent subnets without compromising security. 13 subnets. 43 A node may belong to multiple subnets at the same time. 48 A Subnet Bridge node is a node in a Bluetooth Mesh network that belongs to multiple subnets and has 50 Subnet Bridge node connects the subnets, and allows communication between them by relaying 54 IV Update procedure and propagates updates to other subnets. 55 The secondary subnets, on which messages are relayed, are referred to as *bridged subnets*. 60 The Bridging Table contains the entries for the subnets that are bridged by the node, and is managed 74 Adding or removing subnets [all …]
|
D | shell.rst | 1862 ``mesh models brg subnets-get <Filter> <NetIdx> <StartIdx>`` 1874 * ``NetIdx``: NetKey index of any of the subnets.
|
/Zephyr-latest/include/zephyr/bluetooth/mesh/ |
D | cdb.h | 81 struct bt_mesh_cdb_subnet subnets[SUBNET_COUNT]; member
|
/Zephyr-latest/subsys/bluetooth/mesh/shell/ |
D | brg_cfg.c | 241 SHELL_CMD_ARG(subnets-get, NULL, "<Filter> <NetIdx> <StartIdx>", cmd_bridged_subnets_get,
|
D | shell.c | 1240 for (i = 0; i < ARRAY_SIZE(bt_mesh_cdb.subnets); ++i) { in cdb_print_subnets() 1241 subnet = &bt_mesh_cdb.subnets[i]; in cdb_print_subnets()
|
/Zephyr-latest/doc/releases/ |
D | release-notes-2.3.rst | 1399 * :github:`14647` - IP: Zephyr replies to broadcast ethernet packets in other subnets on the same w…
|
D | release-notes-1.14.rst | 1278 * :github:`14647` - IP: Zephyr replies to broadcast ethernet packets in other subnets on the same w…
|