commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Uevent (9118da8f)
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 9118da8f1179d7d8da9136d690b85af176afe4f0 Author: Antonio Quartulli <a(a)unstable.cc> Date: Sat May 28 16:17:37 2011 +0000 doc: batman-adv/Uevent >--------------------------------------------------------------- 9118da8f1179d7d8da9136d690b85af176afe4f0 batman-adv/Uevent.textile | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/batman-adv/Uevent.textile b/batman-adv/Uevent.textile new file mode 100644 index 00000000..4c1710ba --- /dev/null +++ b/batman-adv/Uevent.textile @@ -0,0 +1,21 @@ +h1. Uevent + +*DRAFT - TO BE FINISHED* + +B.A.T.M.A.N.-Advance can now throw uevents! Thanks to this new feature it is possible to advertise any kind of information to the usespace. +This will probably enable several applications to interact with B.A.T.M.A.N. + +*Function prototype:* + +<pre>int throw_uevent(struct bat_priv *bat_priv, enum uev_type type, enum uev_action action, const char *data);</pre> + +* type: is the class the uevent belongs to. It is possible to specify new classes into B.A.T.M.A.N. to distinguish between not related uevents +* action: is the class related event that has to be signaled +* data: any meaningful payload that need to be sent to the userspace + +*Example:* +* type: GW +* action: ADD/CHANGE/DEL +* data: the gateway MAC address + +This is an example of a class of possible uevents to throw to userspace. In case of default gateway change, a uevent is triggered and sent to the userspace with all the needed data. The action field, in this case, represent the event related to the gateway (e.g. ADD: a default gateway for B.A.T.M.A.N. has been found).

1 0

[doc] backup-redmine/2017-07-13,master: doc: batman-adv/T_X's_Junkyard_–_MGO (1f5f7851)
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 1f5f7851a7cf4987d08e3dd3b80e155017ac4f6b Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat May 28 03:49:48 2011 +0000 doc: batman-adv/T_X's_Junkyard_–_MGO >--------------------------------------------------------------- 1f5f7851a7cf4987d08e3dd3b80e155017ac4f6b "batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" | 2 ++ 1 file changed, 2 insertions(+) diff --git "a/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" "b/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" index 0ee455ca..0d540f8c 100644 --- "a/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" +++ "b/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" @@ -279,6 +279,8 @@ In case the MGO-RR was not dropped yet one of the following four actions needs t * Else the following action needs to be performed: ** Send a unicast OGM response: Forward the last (re)broadcasted OGM for the originator stated in the MGO-RR (which is the OGM received via the currently selected, best router towards the originator or the originator itself) via unicast to the neighbor we received the MGO-RR from. +TODO: Add TTL checks + h4. Receiving an OGM via Unicast TODO

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Uevent (fd4fef44)
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 fd4fef44f0f0e32d26d949353a8b3910b2c9a490 Author: Antonio Quartulli <a(a)unstable.cc> Date: Sat May 28 16:20:07 2011 +0000 doc: batman-adv/Uevent >--------------------------------------------------------------- fd4fef44f0f0e32d26d949353a8b3910b2c9a490 batman-adv/Uevent.textile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/batman-adv/Uevent.textile b/batman-adv/Uevent.textile index 4c1710ba..4fcdf4cb 100644 --- a/batman-adv/Uevent.textile +++ b/batman-adv/Uevent.textile @@ -7,7 +7,8 @@ This will probably enable several applications to interact with B.A.T.M.A.N. *Function prototype:* -<pre>int throw_uevent(struct bat_priv *bat_priv, enum uev_type type, enum uev_action action, const char *data);</pre> +<pre>int throw_uevent(struct bat_priv *bat_priv, enum uev_type type, + enum uev_action action, const char *data);</pre> * type: is the class the uevent belongs to. It is possible to specify new classes into B.A.T.M.A.N. to distinguish between not related uevents * action: is the class related event that has to be signaled

1 0

[doc] backup-redmine/2017-07-13,master: doc: batman-adv/T_X's_Junkyard_–_MGO (b5220bf3)
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 b5220bf39b225cf0f5106e24a54cf5cc544b4a80 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat May 28 03:47:41 2011 +0000 doc: batman-adv/T_X's_Junkyard_–_MGO >--------------------------------------------------------------- b5220bf39b225cf0f5106e24a54cf5cc544b4a80 "batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git "a/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" "b/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" index 9b4e85b3..0ee455ca 100644 --- "a/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" +++ "b/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" @@ -6,7 +6,7 @@ In certain topologies the OGM (Originator Message) protocol can still have sever The purpose of the MGO protocol is to react to (rapidly) decreasing local link qualities and to actively try to find an alternative, loop-free path, while only increasing the overhead on the currently selected and alternative paths. It shall complement the proactive OGM protocol. -The MGO protocol is split into two parts: The Router Alert part to mark the currently selected best path(s) as 'stale' in response to a previously detected emergency event. And the Router Request part to request newer sequence numbers from alternative paths that allow nodes on the marked 'fragile' path to switch to the alternative path safely, e.g. without causing routing loops. +The MGO protocol is split into two parts: The Router Alert part to mark the currently selected best path(s) as 'stale' in response to a previously detected emergency event. And the Router Request part to request newer sequence numbers from alternative paths that allow nodes on the marked 'stale' path to switch to the alternative path safely, e.g. without causing routing loops. h1. Definitions

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (5ce389d3)
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 5ce389d3a572d9b2ba0b8d54b0b0da7cb787ade7 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat May 28 10:28:26 2011 +0000 doc: open-mesh/Download >--------------------------------------------------------------- 5ce389d3a572d9b2ba0b8d54b0b0da7cb787ade7 open-mesh/Download.textile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index fbe35eca..1c729dfb 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -60,9 +60,10 @@ Use emerge to build B.A.T.M.A.N. on your gentoo machine. Following ebuilds are a * "net-misc/batctl":http://packages.gentoo.org/package/net-misc/batctl * "net-misc/batman-adv":http://packages.gentoo.org/package/net-misc/batman-adv -h2. OpenSUSE +h2. openSUSE * "network:utilities / batctl":https://build.opensuse.org/package/show?package=batctl&project=network%253Autilities +* the batman-adv module is available as module in the official kernel packages h2. Building OpenWRT packages

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download: Add (f92dabbe)
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 f92dabbebcc56bbe468a197ea35c37d292bd08a4 Author: Sven Eckelmann <sven(a)narfation.org> Date: Tue May 24 09:33:18 2011 +0000 doc: open-mesh/Download: Add >--------------------------------------------------------------- f92dabbebcc56bbe468a197ea35c37d292bd08a4 open-mesh/Download.textile | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index 0469ff48..aecc74e0 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -49,6 +49,16 @@ Use apt-get (or any other dpkg frontend of choice) to install B.A.T.M.A.N. onto * "batman-adv-dkms":http://packages.debian.org/squeeze/batman-adv-dkms - batman-advanced kernel module 2010.0.0 dkms package for Debian Squeeze to build new modules dynamically (half-automatic) * "linux-2.6":http://packages.debian.org/source/unstable/linux-2.6 - batman-advanced kernel module as "part of the official":http://bugs.debian.org/622361 kernel packages +Similar packages are also available through "Ubuntu universe":https://help.ubuntu.com/community/Repositories/Ubuntu . + + +h2. Gentoo + +Use emerge to build B.A.T.M.A.N. on your gentoo machine. Following ebuilds are available: +* "net-misc/batmand":http://packages.gentoo.org/package/net-misc/batmand +* "net-misc/batman-vis":http://packages.gentoo.org/package/net-misc/batman-vis +* "net-misc/batctl":http://packages.gentoo.org/package/net-misc/batctl +* "net-misc/batman-adv":http://packages.gentoo.org/package/net-misc/batman-adv h2. Building OpenWRT packages

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download: Add link to batctl in OpenSUSE - at least I think it is available there (96731e53)
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 96731e5394a9bf229e532252459fcdc39d56dba6 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat May 28 00:37:21 2011 +0000 doc: open-mesh/Download: Add link to batctl in OpenSUSE - at least I think it is available there >--------------------------------------------------------------- 96731e5394a9bf229e532252459fcdc39d56dba6 open-mesh/Download.textile | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index aecc74e0..fbe35eca 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -60,6 +60,10 @@ Use emerge to build B.A.T.M.A.N. on your gentoo machine. Following ebuilds are a * "net-misc/batctl":http://packages.gentoo.org/package/net-misc/batctl * "net-misc/batman-adv":http://packages.gentoo.org/package/net-misc/batman-adv +h2. OpenSUSE + +* "network:utilities / batctl":https://build.opensuse.org/package/show?package=batctl&project=network%253Autilities + h2. Building OpenWRT packages

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-roaming (4e47bfca)
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 (1798be9c)
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 1798be9cc79922f341017386deeecb7d02e3df8a Author: Antonio Quartulli <a(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

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Client-roaming (86f77c59)
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 86f77c59245d9d57365df53e8068a275a5d8df79 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Thu May 26 01:37:27 2011 +0000 doc: batman-adv/Client-roaming >--------------------------------------------------------------- 86f77c59245d9d57365df53e8068a275a5d8df79 batman-adv/Client-roaming.textile | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/batman-adv/Client-roaming.textile b/batman-adv/Client-roaming.textile index af3181ce..4ea8d202 100644 --- a/batman-adv/Client-roaming.textile +++ b/batman-adv/Client-roaming.textile @@ -6,10 +6,11 @@ The base idea consists in exploiting the new forwarding mechanism for data packe The main idea behind the roaming improvements is to make use of the fact that batman-adv has full control over the payload traffic traveling through the mesh network. In particular, with this mechanism the packet destination is modified along the path, if needed, as the message reaches an up-to-date router. If so data packet is rerouted to the new destination and information in the packet header are updated too (destination and ttvn field) until the mesh network is in sync again. In addition, a roaming advertisement packet is sent to immediately inform the old originator that the client has moved and that it is now located on another node. This message can be seen as an asynchronous update that permits the old node to redirect data packets as soon as they reach it. -h2. Roaming advertisement +h2. Detect a roaming client -The roaming advertisement format: +To detect whether a recently detected non-mesh client is a roaming client or a new client, it is sufficient to search the global translation table for the clients mac address. In case of positive match (the same MAC address is already in the table but pointing to another mesh node) the node has to send a roaming advertisement message to the old mesh node to inform it about the roaming event. +The roaming advertisement format: * Packet type: Initialize this field with the ROAM_ADV packet type. * Version: Set your internal compatibility version. * Destination Address: Address of the host this packet should be forwarded to. @@ -41,14 +42,9 @@ Due to this mechanism, immediately after a roaming the data packets might follow h2. Routing data packets -The basic routing procedure is the same described in the [[Client-announcement]] page. The only difference consists in giving the routing node the possibility of inspect the data packet (to possibly change the destination) even if the TTVN carried by the packet is not less than the one the router knows. -This chance must be given only in a case: the destination node is in *roaming phase*. - -The **tt_poss_change** flag in the originator structure is used for this purpose. It is set tu true in case of receiving a ROAMING-Advertisement from an originator an it is set to false again once a new OGM is received from the same node. - -h2. Detecting a roaming phase +The enhanced data routing is built on top of the data routing procedure described in the [[Client-announcement]] page. When a mesh node receives a roaming advertisement concerning one of its former non-mesh clients it will mark the client entry with the roaming flag. The mesh node sending the roaming advertisement will do the same. This extra flag is needed as long as the translation tables are not in sync and will have to be deactivated once an OGM with the new ttvn arrives. -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. +When payload data reaches either node (new or old mesh node) they will not only check if the translation table version number (ttvn) of the destination host is outdated but also check if the roaming flag is active. If one of the conditions is met the payload traffic is rerouted if necessary. h2. Keeping table consistency @@ -65,9 +61,9 @@ The TT_GLOBAL_ROAM in the tt_global_entry structure will be reset to 0 as soon a h2. Limitations -- **MAC conflict**: In case of more than one node announcing the same client MAC address, each node will interpret this situation as a "continued roaming" and will start sending ROAMING-Advertisement multiple times. To reduce the impact of this problematic scenario a **roaming-protection** has been provided: A client con roam on the same node a fixed amount of times in a fixed length period (look into main.h for the exact values). In case of exceeding the limit, the interested node will not issue any new ROAMING-Advertisement unless the protection period is terminated. +* MAC conflict: In case of more than one node announcing the same client MAC address, each node will interpret this situation as a "continued roaming" and will start sending roaming advertisement messages multiple times. To reduce the impact of this problematic scenario a roaming-protection has been provided: A client can roam on the same node a fixed amount of times in a fixed length period (look into main.h for the exact values). In case of exceeding the limit, the interested node will not issue any new roaming advertisement unless the protection period is terminated. -- **Multiple-roaming in one OGM interval**: In case of a node roaming from node A to B a ROAMING-Advertisement is sent from B to A, but if the client moves again from node B to C, before B issued a new OGM, C will send the ROAMING-Advertisement to A again!! This happens because C doesn't know anything yet about the last client movement. **A possible solution to this problem could consists in implementing a ROAMING-Advertisement forwarding procedure that in scenarios like this make the ROAMING-Advertisement message going through all the steps the client did. By the way this feature is not critical** +* multiple roaming in one OGM interval: In case of a node roaming from node A to B a roaming advertisement is sent from B to A, but if the client moves again from node B to C, before B issued a new OGM, C will send the roaming advertisement to A again! This happens because C doesn't know anything yet about the last client movement. *A possible solution to this problem could consist in implementing a roaming advertisement forwarding procedure that in scenarios like this make the roaming advertisement message going through all the steps the client did. h2. Notes

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017