Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 017460afaa6c9d3c80eb35a6d47f9f83dd1ec429 Author: Antonio Quartulli a@unstable.cc Date: Mon May 2 10:18:31 2011 +0000
doc: batman-adv/Client-announcement
017460afaa6c9d3c80eb35a6d47f9f83dd1ec429 batman-adv/Client-announcement.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/batman-adv/Client-announcement.textile b/batman-adv/Client-announcement.textile index ec93388b..24513ee8 100644 --- a/batman-adv/Client-announcement.textile +++ b/batman-adv/Client-announcement.textile @@ -12,7 +12,7 @@ The current implementation just adds the client mac addresses to the responsible * It can take up to a couple of seconds for a node to roam and being recognised at its new position, depending on the link qualities. A unicast packet sent to the outdated orignator will just be dropped at this node.
-h2. Concept Ideas +h2. The new mechanism
h3. How the announcement works
@@ -27,7 +27,7 @@ h3. How the announcement works * Every node memorizes the last changeset announced within the OGM of each node in the network * A TT-REQUEST can request a complete local table or just a the last sent changeset.
-h4. Guaraneteeing consistency +h3. Guaraneteeing consistency
To be sure to that a node has all the right information, an hash value of the local translation table is spread within the OGM. This value is called TT_CRC.