[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-announcement (902b58d6) - commits - lists.open-mesh.org

14 Jul 2017

Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
...

commit 902b58d6224747d62bfa6f189b83068fd8aab615
Author: Antonio Quartulli a@unstable.cc
Date:   Sun May 22 21:53:10 2011 +0000
doc: batman-adv/Client-announcement
...

902b58d6224747d62bfa6f189b83068fd8aab615
 batman-adv/Client-announcement.textile | 23 +++++++++++++++++------
 1 file changed, 17 insertions(+), 6 deletions(-)

diff --git a/batman-adv/Client-announcement.textile b/batman-adv/Client-announcement.textile
index bcce07a8..c06149a8 100644
--- a/batman-adv/Client-announcement.textile
+++ b/batman-adv/Client-announcement.textile
@@ -35,12 +35,23 @@ This distinction is done using the TT_FULL_TABLE bit of the bitwise **flag field
 The originator that receives the TT_REQUEST message will reply with a TT_RESPONSE to which the node will append the requested data.
The TT_REQUEST message will contain the following fields:
-In particular the TT_REQUEST/TT_REPONSE messages are two subtypes of the TT_QUERY message which has the following fields (only fields related to the TT mechanism have been reported):
-
-<pre><code>uint8_t  flags;
-uint8_t  src[ETH_ALEN];
-uint8_t  ttvn;
-uint16_t tt_data;</code></pre>
+In particular the TT_REQUEST/TT_REPONSE messages are two subtypes of the TT_QUERY message which has the following format:
+
+<pre>
+  0                   1                   2                   3
+  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ | Packet Type   |    Version    |      Destination...           |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ |                         ...Address                            |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ | TTL           |    Flags      |      Source...                |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ |                         ...Address                            |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ |   TTVN        |                  TT_Data                      |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+</pre>
The flag field is used to distinguish between a TT_REQUEST and a TT_RESPONSE and to inform whether the TT_QUERY message is asking for/carrying a full local table or only the last OGM transtable buffer.

    