Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2019-09-17,master

commit 013a64e7d98f6fd391e7b7d12a2288b73ab5fc22 Author: Sven Eckelmann sven@narfation.org Date: Tue Sep 17 10:29:37 2019 +0000

doc: batman-adv/TT-Flags

013a64e7d98f6fd391e7b7d12a2288b73ab5fc22 batman-adv/TT-Flags.textile | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/batman-adv/TT-Flags.textile b/batman-adv/TT-Flags.textile index 27ebca1..ce4c9f4 100644 --- a/batman-adv/TT-Flags.textile +++ b/batman-adv/TT-Flags.textile @@ -6,9 +6,9 @@ h2. Flags overview

This section describes the flags used in the TT code, what they mean and where they are used. There are 3 possible locations where the flags field is used:

- * OGM: there is a flag field within each of the tt_change structs which are sent along with the OGM frames. - * tt_global: these structs are stored in the global hash table and represent the mapping which originator hosts which client. - * tt_local: these structs are stored in the local hash table and represent the the clients which the own node hosts. +* OGM: there is a flag field within each of the tt_change structs which are sent along with the OGM frames. +* tt_global: these structs are stored in the global hash table and represent the mapping which originator hosts which client. +* tt_local: these structs are stored in the local hash table and represent the the clients which the own node hosts.

|_. Name |_. used in |_. Description | | TT_CLIENT_DEL | OGM | The TT_CLIENT_DEL flag is used in the OGM tt_change entries to distinguish whether the entry should be added (no DEL flag set) or deleted (DEL flag set). @@ -53,17 +53,17 @@ Depending on the order of arrival of the OGMs at node E, we have different behav

_Example1: order of arrival: DEL from A, ADD from C, DEL from B, ADD from D_

- * DEL from A: A is removed from the tt_global originator list for X, only B remains. - * ADD from C: C is added to the tt_global originator list for X, now containing B and C - * DEL from B: B is removed from the tt_global originator list for X, only C remains. - * ADD from D: D is added to the tt_global originator list for X, now containing C and D +* DEL from A: A is removed from the tt_global originator list for X, only B remains. +* ADD from C: C is added to the tt_global originator list for X, now containing B and C +* DEL from B: B is removed from the tt_global originator list for X, only C remains. +* ADD from D: D is added to the tt_global originator list for X, now containing C and D

_Example2: order of arrival: DEL from A, DEL from B, ADD from C, ADD from D_

- * DEL from A: A is removed from the tt_global originator list for X, only B remains. - * DEL from B: B is NOT removed from the tt_global originator list for X, it remains but TT_CLIENT_ROAM flag is set for this tt_global entry, and the timer is started. - * ADD from C: C is added to the tt_global originator list for X, B is deleted, the TT_CLIENT_ROAM flag is cleared and the timer is stopped. The list now contains C. - * ADD from D: D is added to the tt_global originator list for X, now containing C and D +* DEL from A: A is removed from the tt_global originator list for X, only B remains. +* DEL from B: B is NOT removed from the tt_global originator list for X, it remains but TT_CLIENT_ROAM flag is set for this tt_global entry, and the timer is started. +* ADD from C: C is added to the tt_global originator list for X, B is deleted, the TT_CLIENT_ROAM flag is cleared and the timer is stopped. The list now contains C. +* ADD from D: D is added to the tt_global originator list for X, now containing C and D

h3. TT_CLIENT_WIFI