Commit: 8a29b59d98b301df8331b4ca4dc9e150e67beee6
Parent: f5c178d1dcc977175a85a5cd0db9774376add08f
Author: Aurelien Jarno <aurelien@aurel32.net>
Committer: Brian Gix <brian.gix@intel.com>
Date: 2019-11-20 01:22:18
Tree: 8049bc5de938b333241b3a70e21608cd4f199c0f

mesh: fix node default TTL There is a confusion between the node default TTL (section 4.2.7) and the publish TTL (section 4.2.2.5): - The node default TTL can only take values 0x00, and 0x02 to 0x7f. The value 0xff is not prohibited. - The publish TTL can take values 0x00 to 0x7f, as well as 0xff which means use the node default TTL. Currently the default node TTL is set to 0xff (DEFAULT_TTL), and read_default_ttl() also allows such a value. This patch fixes that to use 0x7f (TTL_MASK) as the default value instead. Note that the code handling OP_CONFIG_DEFAULT_TTL_SET correctly use 0x7f (TTL_MASK) for the upper allowed limit.

Diffstat

M mesh/mesh-config-json.c | 2 +-
M mesh/node.c | 4 ++- -

2 files changed, 3 insertions(+), 3 deletions(-)

View Full Diff | Patch