commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: attachments/alternation_chain.dia (b7159261)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit b715926171f895f0e7082b1ec220c6a42f4584f8 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun May 22 12:17:04 2011 +0000 doc: attachments/alternation_chain.dia >--------------------------------------------------------------- b715926171f895f0e7082b1ec220c6a42f4584f8 attachments/alternation_chain.dia | Bin 0 -> 1826 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/attachments/alternation_chain.dia b/attachments/alternation_chain.dia new file mode 100644 index 00000000..d1e3855f Binary files /dev/null and b/attachments/alternation_chain.dia differ

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-roaming (81bfc2d7)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 81bfc2d7843ec23498b34b4e25cbe7a72ef92660 Author: Antonio Quartulli <a(a)unstable.cc> Date: Sun May 22 16:26:45 2011 +0000 doc: batman-adv/Client-roaming >--------------------------------------------------------------- 81bfc2d7843ec23498b34b4e25cbe7a72ef92660 batman-adv/Client-roaming.textile | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/batman-adv/Client-roaming.textile b/batman-adv/Client-roaming.textile index a67f9c13..80245924 100644 --- a/batman-adv/Client-roaming.textile +++ b/batman-adv/Client-roaming.textile @@ -17,6 +17,10 @@ Exploiting this mechanism, immediately after a roaming the data packets will fol This strategy will help to avoid to lose packets that are still flowing to the old node in the time that the source get updated using the next OGMs. +h2. Forwarding data packets + +(to add tt_poss_change description) + h2. Detecting a roaming phase To detect a roaming phase, a node in case of new local client detection will look into its global translation table for the address of the new host. In case of positive match (the same MAC address is already in the table but pointing to another originator) the new mesh node will send a **ROAMING-Advertisement** message to the old node serving this client so that it will be able to update its global table and possibly redirect packets to the new mesh node.

1 0

[doc] backup-redmine/2017-07-13, master: doc: attachments/interface_detection.dia (2c290393)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 2c290393934827ce96e9a55c7f7e4b96e0ba5c48 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun May 22 12:17:04 2011 +0000 doc: attachments/interface_detection.dia >--------------------------------------------------------------- 2c290393934827ce96e9a55c7f7e4b96e0ba5c48 attachments/interface_detection.dia | Bin 0 -> 1723 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/attachments/interface_detection.dia b/attachments/interface_detection.dia new file mode 100644 index 00000000..21b99550 Binary files /dev/null and b/attachments/interface_detection.dia differ

1 0

[doc] backup-redmine/2017-07-13, master: doc: attachments/bonding_roundrobin.dia (c63de10f)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit c63de10ff9e81bec408c2858c60c30fa936399a4 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun May 22 12:17:04 2011 +0000 doc: attachments/bonding_roundrobin.dia >--------------------------------------------------------------- c63de10ff9e81bec408c2858c60c30fa936399a4 attachments/bonding_roundrobin.dia | Bin 0 -> 1799 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/attachments/bonding_roundrobin.dia b/attachments/bonding_roundrobin.dia new file mode 100644 index 00000000..5a572ddd Binary files /dev/null and b/attachments/bonding_roundrobin.dia differ

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-announcement (f2857648)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-announcement (24a56bfb)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 24a56bfb24f88e7c10196ac5e4bdebed485f54d6 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun May 22 20:04:27 2011 +0000 doc: batman-adv/Client-announcement >--------------------------------------------------------------- 24a56bfb24f88e7c10196ac5e4bdebed485f54d6 batman-adv/Client-announcement.textile | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/batman-adv/Client-announcement.textile b/batman-adv/Client-announcement.textile index b1e69950..dd13b78f 100644 --- a/batman-adv/Client-announcement.textile +++ b/batman-adv/Client-announcement.textile @@ -4,13 +4,13 @@ Each mesh protocol offering network access to non-mesh clients needs a 'client a h2. The local translation table -Every client MAC address that is recognised 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 because when a node wants to contact a particular client, thank 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: each time the node decide to spread the table around, if something happened since last spread (a client has been added/removed), the ttvn is incremented by one. -In this way, two tables belonging to the same node can be chronologically ordered and it is moreover possible to decide whether they are different or not without checking all the entries. Moreover the translation table version number if a new OGM field and it will contain the originator ttvn value at the moment of sending. +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 value of the local table to allow the receiving nodes to quickly decide whether they tables are in sync or not. h2. The global translation table -Every node in the network has to store all the other node local tables. To achieve this, another table is needed: the "global translation table". It is a set of entries where each of them contains the client MAC address and a pointer to the originator that is currently announcing it. +Every node in the network has to store all the other node's local tables. To achieve this, another table is needed: the "global translation table". It is a set of entries where each contains the client MAC address and a pointer to the originator that is currently announcing it. h2. Updating the tables

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-announcement (b613e35b)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit b613e35b4a9a0d1146a2dc30885f5edc088d6f5c Author: Antonio Quartulli <a(a)unstable.cc> Date: Thu May 19 11:25:06 2011 +0000 doc: batman-adv/Client-announcement >--------------------------------------------------------------- b613e35b4a9a0d1146a2dc30885f5edc088d6f5c batman-adv/Client-announcement.textile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/batman-adv/Client-announcement.textile b/batman-adv/Client-announcement.textile index 68145422..901b6ba8 100644 --- a/batman-adv/Client-announcement.textile +++ b/batman-adv/Client-announcement.textile @@ -118,6 +118,8 @@ This behaviour slightly helps in case of roaming: a client moved from a mesh nod h2. Limitations +- **MAC conflict**: in case of several node announcing the same client MAC address, the global table will be continuously updated leading to a route flip (towards the client) on all nodes + h2. Notes A research project has been done on this topic and it will be linked on this page as soon as it get ready. \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-roaming (7f7001a3)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 7f7001a3c3bac178d26e41d6e30f94c154706f02 Author: Antonio Quartulli <a(a)unstable.cc> Date: Thu May 19 11:19:08 2011 +0000 doc: batman-adv/Client-roaming >--------------------------------------------------------------- 7f7001a3c3bac178d26e41d6e30f94c154706f02 batman-adv/Client-roaming.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Client-roaming.textile b/batman-adv/Client-roaming.textile index 2e0d0694..a67f9c13 100644 --- a/batman-adv/Client-roaming.textile +++ b/batman-adv/Client-roaming.textile @@ -28,7 +28,7 @@ As described [[Client-announcement|here]] each node computes its local tt_crc va In particular, a node receiving a Roaming-Advertisement message will track this change as a simple removal and will send it within the next OGM. The receiver node has to **do not delete** this client immediately, otherwise it will lose any route towards it. So the idea is to keep the client entry in the nodes global tables. By the way this solution could lead to an inconsistent state: if client C roams from A to B, A won't have C in its local table any more, but nodes keeping this entry pointing to A will then compute a wrong (global) tt_crc value for A (they are using C in the computation). -To solve this issue, a new flags field has been added to the tt_change and the tt_global_entry structure. In particular, every **del** change generated by a roaming event will have the TT_CHANGE_ROAM bit set so that receiving node can set the corresponding TT_GLOBAL_ROAM flag in the tt_global_entry it is going to modify/create. This flag will slightly modify the tt_crc computation for global tables: entry with TT_GLOBAL_ROAM set will not be used for the computation to reflect the state of the originator's local table keeping a valid route to clients at the same time. +To solve this issue, a new flags field has been added to the tt_change and the tt_global_entry structure. In particular, every **delete** change generated by a roaming event will have the TT_CHANGE_ROAM bit set so that receiving node can set the corresponding TT_GLOBAL_ROAM flag in the tt_global_entry it is going to modify/create. This flag will slightly modify the tt_crc computation for global tables: entry with TT_GLOBAL_ROAM set will not be used for the computation to reflect the state of the originator's local table keeping a valid route to clients at the same time. The TT_GLOBAL_ROAM in the tt_global_entry structure will be reset to 0 as soon as a new OGM containing an **add** event for that client is received.

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-announcement (aaa93e3c)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit aaa93e3ce3a62cb301dbacba1ec63112e2c62802 Author: Antonio Quartulli <a(a)unstable.cc> Date: Thu May 19 15:17:15 2011 +0000 doc: batman-adv/Client-announcement >--------------------------------------------------------------- aaa93e3ce3a62cb301dbacba1ec63112e2c62802 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 901b6ba8..5c725d6e 100644 --- a/batman-adv/Client-announcement.textile +++ b/batman-adv/Client-announcement.textile @@ -118,7 +118,7 @@ This behaviour slightly helps in case of roaming: a client moved from a mesh nod h2. Limitations -- **MAC conflict**: in case of several node announcing the same client MAC address, the global table will be continuously updated leading to a route flip (towards the client) on all nodes +- **MAC conflict**: in case of several node announcing the same client MAC address, the global table of each node will be continuously updated leading to a route flip (towards the client) on all nodes h2. Notes

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download: Remove batman-adv-* packages - they must be removed from Debian. see http://bugs.debian.org/627413 (aa4de6cc)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit aa4de6cccdcdb8ecd29cffed4d5e52e9f79b216e Author: Sven Eckelmann <sven(a)narfation.org> Date: Fri May 20 14:37:45 2011 +0000 doc: open-mesh/Download: Remove batman-adv-* packages - they must be removed from Debian. see http://bugs.debian.org/627413 >--------------------------------------------------------------- aa4de6cccdcdb8ecd29cffed4d5e52e9f79b216e open-mesh/Download.textile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index 26f46916..2b10c532 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -44,9 +44,7 @@ h2. Debian Use apt-get (or any other dpkg frontend of choice) to install B.A.T.M.A.N. onto your debian machine. Following packages are available: * "batmand":http://packages.debian.org/sid/batmand - batman 0.3.2 -* "batman-adv-source":http://packages.debian.org/sid/batman-adv-source - batman-advanced kernel 2011.0.0 module source (installable via "module-assistant":http://packages.debian.org/sid/module-assistant) -* "batman-adv-dkms":http://packages.debian.org/sid/batman-adv-dkms - batman-advanced kernel module 2011.0.0 dkms package to build new modules dynamically (half-automatic) -* "batctl":http://packages.debian.org/sid/batctl - batctl 2011.0.0 +* "batctl":http://packages.debian.org/sid/batctl - batctl 2011.1.0 h2. Building OpenWRT packages

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017