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

On branches: backup-redmine/2017-07-13,master

commit 1798be9cc79922f341017386deeecb7d02e3df8a Author: Antonio Quartulli a@unstable.cc Date: Mon May 23 10:10:23 2011 +0000

doc: batman-adv/Client-announcement

1798be9cc79922f341017386deeecb7d02e3df8a batman-adv/Client-announcement.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/batman-adv/Client-announcement.textile b/batman-adv/Client-announcement.textile index 6a626c20..5a3de4b5 100644 --- a/batman-adv/Client-announcement.textile +++ b/batman-adv/Client-announcement.textile @@ -6,7 +6,7 @@ h2. The local translation table

Every client MAC address that is recognized through the mesh interface will be stored in a node local table called "local translation table" which will contain all the clients the node is currently serving. This table is the information a node has to spread among the network in order to make clients reachable. This is because when a node wants to contact a particular client, thanks to this information, it knows the originator it has to send the data to. Each node local table has a particular attribute: the translation table version number (ttvn). The value of this attribute represents the version of the table that is incremented by one each time the local table changes (a client has been added/removed). For optimization reasons all changes which happen within the same OGM interval are aggregated into a single ttvn. -Every OGM broadcast contains the current ttvn and a crc16 checksum value of the local table to allow the receiving nodes to quickly decide whether they tables are in sync or not. +Every OGM broadcast contains the current ttvn and a crc16 checksum value of the local table to allow the receiving nodes to quickly decide whether the tables are in sync or not.

h2. The global translation table