bluez/mesh
Khem Raj 7104f37735 mesh: Move local basename into utility file
Defining an override via a missing.h can prove difficult when a file
needs to use basename and dirname both the APIs and needs to include
libgen.h for them, in such situations there will be signature clash
for basename function.
2024-09-19 13:01:52 -04:00
..
agent.c mesh: const annotate misc data 2024-01-19 15:46:14 -05:00
agent.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
appkey.c mesh: Reply error if appkey added for wrong netkey 2022-09-23 10:06:37 -07:00
appkey.h mesh: Make key_aid and net_key_id naming consistent 2022-02-04 12:12:27 -08:00
bluetooth-mesh.conf mesh: Allow sending on org.bluez.mesh.Provisioner1 2019-07-18 09:47:14 -07:00
bluetooth-mesh.service.in build: handle relative libexecdir instances 2024-02-20 08:51:26 -05:00
bluetooth-meshd.rst.in mesh: Update the behavior of --io option 2023-05-12 11:22:14 -07:00
cfgmod-server.c mesh: Fix build error 2023-06-13 13:32:11 -07:00
cfgmod.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
crypto.c mesh: Remove unused byte swap for ScanBuild 2023-01-30 16:14:41 -08:00
crypto.h mesh: Rename parameter list per crypto usage 2023-01-30 16:14:41 -08:00
dbus.c mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
dbus.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
error.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
friend.c mesh: Correct size of friend cache 2022-10-06 13:34:20 -07:00
friend.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
keyring.c mesh: Add Remote Provisioning 2023-01-30 16:14:41 -08:00
keyring.h mesh: Add Remote Provisioning 2023-01-30 16:14:41 -08:00
main.c mesh: Update the behavior of --io option 2023-05-12 11:22:14 -07:00
manager.c mesh: Fix uninitialized memory usage 2023-03-14 14:34:36 -07:00
manager.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
mesh-config-json.c mesh: Move local basename into utility file 2024-09-19 13:01:52 -04:00
mesh-config.h mesh: Add storage of Mesh Private Beacon settings 2023-01-30 16:14:41 -08:00
mesh-defs.h mesh: Update AppKeys on transition to Phase 0 2021-01-04 08:58:37 -08:00
mesh-io-api.h mesh: Tighten IO and fix out-of-bounds array access 2023-04-03 13:29:00 -07:00
mesh-io-generic.c mesh: Fix check for active scan when using generic IO 2023-10-16 17:33:46 -07:00
mesh-io-generic.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
mesh-io-mgmt.c mesh: Tighten IO and fix out-of-bounds array access 2023-04-03 13:29:00 -07:00
mesh-io-mgmt.h mesh: Add new kernel MGMT based IO transport 2022-09-26 13:14:47 -07:00
mesh-io-unit.c mesh: Tighten IO and fix out-of-bounds array access 2023-04-03 13:29:00 -07:00
mesh-io-unit.h mesh: Add unit test IO 2021-04-10 10:28:14 -07:00
mesh-io.c mesh: Update the behavior of --io option 2023-05-12 11:22:14 -07:00
mesh-io.h mesh: Tighten IO and fix out-of-bounds array access 2023-04-03 13:29:00 -07:00
mesh-main.conf mesh: Add mesh-main.conf file with general mesh configuration 2019-12-16 14:52:36 -08:00
mesh-mgmt.c mesh: Update the behavior of --io option 2023-05-12 11:22:14 -07:00
mesh-mgmt.h mesh: Update the behavior of --io option 2023-05-12 11:22:14 -07:00
mesh.c mesh: Add new kernel MGMT based IO transport 2022-09-26 13:14:47 -07:00
mesh.h mesh: Add new kernel MGMT based IO transport 2022-09-26 13:14:47 -07:00
model.c mesh: Add internal Mesh Private Beacon model 2023-01-30 16:14:41 -08:00
model.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
net-keys.c mesh: Add internal Mesh Private Beacon model 2023-01-30 16:14:41 -08:00
net-keys.h mesh: Add internal Mesh Private Beacon model 2023-01-30 16:14:41 -08:00
net.c mesh: Switch beaconing net key 2023-01-30 16:14:41 -08:00
net.h mesh: Add Tx/Rx support of Mesh Private Beacons 2023-01-30 16:14:41 -08:00
node.c mesh: Fix node when loading from storage 2023-03-12 11:57:54 -07:00
node.h mesh: Add internal Mesh Private Beacon model 2023-01-30 16:14:41 -08:00
org.bluez.mesh.service build: Add support for systemd bluetooth-mesh service 2019-06-06 11:58:22 -07:00
pb-adv.c mesh: Fix integer overflow due to cast operation 2024-07-08 10:39:21 -04:00
pb-adv.h mesh: Add Remote Provisioning 2023-01-30 16:14:41 -08:00
prov-acceptor.c mesh: Add Remote Provisioning 2023-01-30 16:14:41 -08:00
prov-initiator.c mesh: Avoid accessing array out-of-bounds 2024-07-03 10:36:34 -04:00
prov.h mesh: Add Remote Provisioning 2023-01-30 16:14:41 -08:00
provision.h mesh: Add Remote Provisioning 2023-01-30 16:14:41 -08:00
prv-beacon.h mesh: Add Mesh Private Beacon server 2023-01-30 16:14:41 -08:00
prvbeac-server.c mesh: Add internal Mesh Private Beacon model 2023-01-30 16:14:41 -08:00
README mesh: ELL encrypt dependancy README section added 2019-05-31 16:46:34 -07:00
remprv-server.c mesh: Don't send Prov Failed on non-existant links 2023-03-15 18:12:38 -07:00
remprv.h mesh: Add Remote Provisioning 2023-01-30 16:14:41 -08:00
rpl.c mesh: Move local basename into utility file 2024-09-19 13:01:52 -04:00
rpl.h mesh: Add SPDX License Identifier 2020-09-21 16:19:35 -07:00
util.c mesh: Move local basename into utility file 2024-09-19 13:01:52 -04:00
util.h mesh: Move local basename into utility file 2024-09-19 13:01:52 -04:00

Bluetooth Mesh Daemon
*********************

Copyright (C) 2019  Intel Corporation. All rights reserved.

Compilation and installation
============================

In addition to main BlueZ requirements, MeshCtl needs the following:
	- json-c library

Configuration and options
=========================

	--enable-mesh

		Build mesh daemon and other Bluetooth Mesh based tools

Current implementation of the mesh daemon requires exclusive access to
a Bluetooth controller.
The AutoEnable option in the installed main.conf should be set to "false".

Storage
=======

Default storage directory is /var/lib/bluetooth/mesh.

The directory contains the provisioned nodes configurations.
Each node has its own subdirectory, named after node's Device UUID (32-digit
hexadecimal string) that is generated by the application that created a node.

Each subdirectory contains the following files:
	- node.json:
		node configuration and is populated by the
		daemon based on the configuration commands from a
		provisioner/configuration client
	- node.json.bak:
		a backup that the last known good node configuration.
	- seq_num:
		File containing next sequence number to use
	- seq_num.bak:
		Backup of the sequence number. This may be larger than the
		actual sequence number being used at runtime, to prevent re-use
		of sequence numbers in the event of an unexpected restart.
	- ./rpl/:
		Directory to store the sequence numbers of remote nodes, as
		required by Replay Protection List (RPL) parameters.
		- xxxx:
			Files named for remote Unicast addresses, and contain
			last received iv_index + seq_num from each SRC address.
	- ./dev_keys/:
		Directory to store remote Device keys. This is only created/used
		by Configuration Client (Network administration) nodes.
		- xxxx:
			Files named for remote Unicast addresses, and contains
			16 octet key.
	- ./net_keys/:
		Directory to store network subnet keys. This is only
		created/used by Configuration Client (Network administration)
		nodes.
		- xxx:
			Files named for subnet index, and contains key refresh
			phase, and old/new versions of the key.
	- ./app_keys/:
		Directory to store application keys. This is only created/used
		by Configuration Client (Network administration) nodes.
		- xxx:
			Files named for application index, and contains bound
			subnet index, and old/new versions of the key.

The node.json and node.json.bak are in JSON format. All other files are stored
in little endian binary format.

Known Issues
============

Bluetooth Mesh makes heavy usage of AEAD-AES_CCM encryption, which is
implemented in the Linux kernel on most platforms. Some platforms, including
those with kernel versions including and prior to v4.8, did *not* correctly
implement the AEAD encryption routines. If Mesh is to be ported to such a
system, it will be the responsibility of the vendor to provide support for
AEAD-AES_CCM encryption by some other method.

Support for the required AEAD routines can be determined by running the unit
tests provided with the ELL libraries used by Mesh. Specifically, the tests
found in .../ell/unit/test-cipher.c

Information
===========

Mailing lists:
	linux-bluetooth@vger.kernel.org

For additional information about the project visit BlueZ web site:
	http://www.bluez.org