commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/DistributedArpTable (01757064)
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 0175706464a8e87804fa4d4eacbba200cf7e94ba Author: Antonio Quartulli <a(a)unstable.cc> Date: Wed Mar 7 01:02:18 2012 +0000 doc: batman-adv/DistributedArpTable >--------------------------------------------------------------- 0175706464a8e87804fa4d4eacbba200cf7e94ba batman-adv/DistributedArpTable.textile | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/batman-adv/DistributedArpTable.textile b/batman-adv/DistributedArpTable.textile index 2a28d1c4..d3e102e6 100644 --- a/batman-adv/DistributedArpTable.textile +++ b/batman-adv/DistributedArpTable.textile @@ -52,3 +52,7 @@ Whenever a node wants to retrieve some data (e.g. due to an ARP request by its o h2. Technical details +# _Incoming ARP Request_: +# _Outgoing ARP Request_: +# _Incoming ARP Reply_: +# _Outgoing ARP Reply_: \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Multi-link-optimize-old (3ebc1182)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Doc-overview (180e2f22)
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 180e2f220a505c2fb39dcd2de7f09ef7af05e9c0 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Feb 20 11:15:31 2012 +0000 doc: batman-adv/Doc-overview >--------------------------------------------------------------- 180e2f220a505c2fb39dcd2de7f09ef7af05e9c0 batman-adv/Doc-overview.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Doc-overview.textile b/batman-adv/Doc-overview.textile index f2615dd9..cf68dd26 100644 --- a/batman-adv/Doc-overview.textile +++ b/batman-adv/Doc-overview.textile @@ -17,7 +17,7 @@ h2. Features * [[bridge-loop-avoidance|Bridge loop avoidance]] - Document explaining the bridge loop avoidance implemented in batman-adv. * [[multi-link-optimize|Multi-Link Optimization]] - how to optimize traffic by using multiple links * [[VisAdv|Visualizing the 2nd layer]] - Creating graphics of the layer 2 network and differences to the layer 3 vis output explained. -* [[ap-isolation|AP Isolation]] - How to prevent wifi-client to wifi-client communications. +* [[ap-isolation|AP Isolation]] - How to prevent wifi-client to wifi-client communication. h2. Troubleshooting

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/SubmittingLinux (6e1363a6)
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 6e1363a616e9332144a844d1a60f1481cc42f749 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Tue Feb 28 12:29:24 2012 +0000 doc: batman-adv/SubmittingLinux >--------------------------------------------------------------- 6e1363a616e9332144a844d1a60f1481cc42f749 batman-adv/SubmittingLinux.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/SubmittingLinux.textile b/batman-adv/SubmittingLinux.textile index 0b5ab926..b1104b30 100644 --- a/batman-adv/SubmittingLinux.textile +++ b/batman-adv/SubmittingLinux.textile @@ -328,7 +328,7 @@ Applying: batman-adv: adapting source version to revised versioning scheme Applying: batman-adv: Add include guards to all header files '-(%25)-(batman-adv/next)> git diff merge/master -- net/batman-adv/ '-(%25)-(batman-adv/next)> git push -'-(%25)-(batman-adv/next)> git request-pull 12513b76a021e5b41a9d5d5981da75dfd6480890 git://git.open-mesh.org/linux-merge.git > shortlog +'-(%25)-(batman-adv/next)> git request-pull 12513b76a021e5b41a9d5d5981da75dfd6480890 git://git.open-mesh.org/linux-merge.git batman-adv-for-davem > shortlog '-(%25)-(batman-adv/next)> git send-email --compose --to=davem(a)davemloft.net --cc=netdev(a)vger.kernel.org --cc=b.a.t.m.a.n(a)lists.open-mesh.org 00*.patch </pre>

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Ap-isolation (da3c19b9)
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 da3c19b97383496e2f9dc96c44f8a557c6ad23b5 Author: Antonio Quartulli <a(a)unstable.cc> Date: Tue Feb 21 21:09:51 2012 +0000 doc: batman-adv/Ap-isolation >--------------------------------------------------------------- da3c19b97383496e2f9dc96c44f8a557c6ad23b5 batman-adv/Ap-isolation.textile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/batman-adv/Ap-isolation.textile b/batman-adv/Ap-isolation.textile index 546156ed..95759ea7 100644 --- a/batman-adv/Ap-isolation.textile +++ b/batman-adv/Ap-isolation.textile @@ -19,7 +19,9 @@ batctl ap 1 </pre> To disable it, just switch 1 to 0 -Note that packets are checked either at the sender or the receiver node, therefore, if at least one of those have AP-Isolation enabled, the communication is forbidden. However we strongly suggest to enable the AP-Isolation on all the nodes in order to prevent wasting of resources. (E.g. send of data over the mesh knowing that it is going to be dropped at the receiver.) +Note that packets are checked either at the sender or the receiver node, therefore, if at least one of those have AP-Isolation enabled, the communication is forbidden. However we strongly suggest to enable the AP-Isolation on all the nodes in order to prevent wasting of resources. (E.g. send of data over the mesh knowing that it is going to be dropped at the receiver) + +Remember that B.A.T.M.A.N.-Advanced AP-Isolation will provide "inter-meshnode communications" prevention only. Therefore if you want to block communications between clients connected to the same access point (actually mesh node) you may want to enable the "class AP-Isolation" function provided by the access point itself. h3. Technical details

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/RIP (3f24612a)
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 3f24612a4b96b778a33828fd5e66bf60f95fd00a Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Fri Feb 24 00:14:16 2012 +0000 doc: batman-adv/RIP >--------------------------------------------------------------- 3f24612a4b96b778a33828fd5e66bf60f95fd00a batman-adv/RIP.textile | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/batman-adv/RIP.textile b/batman-adv/RIP.textile new file mode 100644 index 00000000..f863735b --- /dev/null +++ b/batman-adv/RIP.textile @@ -0,0 +1,50 @@ +h1. RIP Protocol (Rest in Peace) + +_The original idea from Linus has been discussed and enhanced by an international committee in December 2011 ... in a pub in Berlin while drinking some nice beer :) The draft presented here may therefore be incomplete, ideas and volunteers for implementation welcome!_ + +h2. Background + +The new [[Ogm-v2|OGM protocol in BATMAN V]] is designed to send OGMs at much lower regular intervals than BATMAN IV, because we split the local link detection part off into ELP. The general idea is to reduce overhead of messages flooded through the network. The disadvantage is that reaction to link failures will also become slower. This RIP protocol (maybe we need a better name?) is designed to react to drastic link changes or outages. It is an extension to the new OGM protocol and works (only) along with it. + +h2. Algorithm Idea + +We discuss the situation at an example: + +h3. Situation + +!circle-v2.png! + +The link between the nodes N2 and N3 suddenly breaks. Unfortunately, this was the route packets where taking on their way from node B to node A. We now could wait until OGMs are flooded on the alternative path to B (or even N3) and replace the (now broken) path. With the new OGM protocol and intervals of 5-10 seconds, this can take some time. On the other hand, ELP sends messages much more often and can detect the link change fast - locally. The task is to globally inform the mesh about the changed situation. + +h3. Death Notes + +N3 will detect that the link to node N2 through ELP. This does not necessarily lead to route deletion directly, as we may reach many Originators through this link (A, N1, N2, ...). As soon as we receive a frame on N3 which is to be sent over this link (e.g. B->A), we broadcast a *death note* for OGM A. This death note means that N3 can no longer serve as router for A. We also delete our stored router for this Originator. + +All nodes who receive the death note and had chosen the sender as router will know that their route is now invalid. In our example, N4 will know that it can not reach A via N3 anymore. A node who receives this message and had the sender chosen as router will also delete its routing entry and will broadcast the death note again - other nodes in their proximity will also know that this node can not serve as a router anymore. In our example, N4 will broadcast the death note too and delete its routing entry. N5 will get the death note, delete the route, and broadcast a death note. B will receive the death note from N5 and does the same. + +h3. OGM Update Request + +At some point, other nodes will also receive the death note who have a still working path towards A (or at least believe so). In our example, N10 will receive the death note from B, but it does not use B as router for A - the selected router is N9. In the case that it (still) has a route to A, so it will send an OGM Update Request via Unicast to its router N9 with final destination A. OGM Update requests are simply passed from node to node until they reach their final destination A. As soon as A receives this OGM Update Request, it will immediately broadcast a new OGM with a new sequence number. + +h3. Back Propagation + +The new OGM from A will be flooded as usual through the mesh. It gets interesting for the nodes who had previously lost their route (N3, N4, N5 and B): They can immediately acquire a new, valid (but maybe suboptimal) route to A, thus get communication working again. + +h2. Discussion + +From the algorithm sketch, we can see: + + * we can promptly react to link outages - as soon as ELP (or some other underlying mechanisms) detects it. + * the death notes are broadcasted only through the affected part of the mesh. Outside nodes use Unicast to reach the Originator - this saves bandwidth + * we can keep long originator interval and still react to changes fast - at least negative ones. + +h3. Death Note packet format + +Death Notes and OGM Update Requests may share a packet type and be distinguished by a flag. They basicly contain: + * the affected Originator Address (either used as subject of the death note or final destination) + * TTL + * (maybe?) last valid OGM + +h3. Optimization Ideas + + * we may also send the last valid OGM from a node which is not affected by a death note - but only after making sure that the connection to the destination still works (e.g. by using a ping). This would require some more state to be saved.

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Doc-overview (bec5e7bf)
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 bec5e7bfdc233ad8edc02d664b41ce42f2d5d636 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Feb 20 06:55:21 2012 +0000 doc: batman-adv/Doc-overview >--------------------------------------------------------------- bec5e7bfdc233ad8edc02d664b41ce42f2d5d636 batman-adv/Doc-overview.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Doc-overview.textile b/batman-adv/Doc-overview.textile index cd4e6bd6..f2615dd9 100644 --- a/batman-adv/Doc-overview.textile +++ b/batman-adv/Doc-overview.textile @@ -17,7 +17,7 @@ h2. Features * [[bridge-loop-avoidance|Bridge loop avoidance]] - Document explaining the bridge loop avoidance implemented in batman-adv. * [[multi-link-optimize|Multi-Link Optimization]] - how to optimize traffic by using multiple links * [[VisAdv|Visualizing the 2nd layer]] - Creating graphics of the layer 2 network and differences to the layer 3 vis output explained. -* [[ap-isolation|AP Isolation]] - How to avoid wifi-client to wifi-client communications. +* [[ap-isolation|AP Isolation]] - How to prevent wifi-client to wifi-client communications. h2. Troubleshooting

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/DistributedArpTable (a34e7f40)
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 a34e7f4063201d0712417a94364596a48af268e5 Author: Antonio Quartulli <a(a)unstable.cc> Date: Wed Feb 22 11:59:44 2012 +0000 doc: batman-adv/DistributedArpTable >--------------------------------------------------------------- a34e7f4063201d0712417a94364596a48af268e5 batman-adv/DistributedArpTable.textile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/batman-adv/DistributedArpTable.textile b/batman-adv/DistributedArpTable.textile index 44b38302..53dab872 100644 --- a/batman-adv/DistributedArpTable.textile +++ b/batman-adv/DistributedArpTable.textile @@ -17,4 +17,8 @@ gets higher if the packet to send is of type broadcast (this is due to the MAC l like the ARP Request. Assuming to be in a fairly sparse wireless mesh network, an ARP Request could get lost several times before being able to find its destination, thus dramatically increasing the latency of establishing an IP connection. -h2. How DAT \ No newline at end of file +h2. DHT basics + +!dat_dht-90.png! + +h2. How DAT merges ARP and the DHT \ No newline at end of file

1 0

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

14 Jul '17

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017