commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (94027592)
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 94027592987e77db50f550b2d1c0368eb90f0c01 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Sun Nov 27 17:18:51 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 94027592987e77db50f550b2d1c0368eb90f0c01 open-mesh/BranchesExplained.textile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index a5f0abb2..0bf98d80 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -15,8 +15,7 @@ h2. batmand Historically, the first implementation of the B.A.T.M.A.N. routing protocol was a user space daemon named batmand. Batmand operates on layer 3 (IP layer) of the OSI model by altering the routing table and offers everything you would expect from a standard routing daemon. Almost all real-world implementations of mesh routing algorithms have started on layer 3 - and most of them still work exclusively on layer 3 today. Check our [[UserDocs|docs]] section if you want to learn more about is capabilities. -Note: Basically all B.A.T.M.A.N. developers except me (Elektra) consider batmand obsolete. It is true that there haven't been any changes in batmand in a while. However batmand is stable and it is used by at least two Open-Source projects. "Villagetelco":http://www.villagetelco.org uses batmand in the VT firmware version of the Mesh-Potato device for VOIP mesh networks. (There is a second firmware for the Mesh-Potato named SECN, which uses batman-adv). The "Serval project": http://www.servalproject.org uses batmand on smartphones. Recently the Serval project has received a grant to finance work on improving the scalability of B.A.T.M.A.N. - +Note: Basically all B.A.T.M.A.N. developers except me (Elektra) consider batmand obsolete. It is true that there haven't been any changes in batmand in a while. However batmand is stable and it is used by at least two Open-Source projects. "Villagetelco":http://www.villagetelco.org uses batmand in the VT firmware version of the Mesh-Potato device for VOIP mesh networks. (There is a second firmware for the Mesh-Potato named SECN, which uses batman-adv). The "Serval project": http://www.servalproject.org uses batmand on smartphones. h2. BMX

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (63a2a005)
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 63a2a005dda1d2f62381a392f46bd7a3c9ca3990 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Sun Nov 27 17:02:39 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 63a2a005dda1d2f62381a392f46bd7a3c9ca3990 open-mesh/BranchesExplained.textile | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 07bb5223..59745484 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -13,11 +13,9 @@ Example: batmand 0.2 uses the B.A.T.M.A.N. III routing algorithm. h2. batmand +Historically, the first implementation of the B.A.T.M.A.N. routing protocol was named batmand, a user-space daemon. Batmand operates on layer 3 (IP layer) of the OSI model and offers everything you would expect from a standard routing daemon. Almost all real-world implementations of mesh routing algorithms have started on layer 3 - and most of them still work exclusively on layer 3. Check our [[UserDocs|docs]] section if you want to learn more about is capabilities. -The batman userspace daemon has been the first implementation of the B.A.T.M.A.N. routing protocol. In the early stages of the project it allowed us to easily experiment with the design of the protocol but also to be used in real world deployments. It operates on layer 3 (IP layer) and offers everything you would expect from a standard routing daemon. Check our [[UserDocs|docs]] section if you want to learn more about is capabilities. - -Note: For historical & support reasons the sources and documentation of batmand are still available. However, if you are about to decide whether you go with batmand or batman-adv, consider batmand obsolete. There has been no active batmand development for years as the layer 2 concept (batman-adv) has proven to be the better path forward. - +Note: Basically all developers except me (Elektra) consider batmand obsolete, because there hasn't been any changes in batmand in a while. However batmand is stable and it is used by at least two Open-Source projects. "Villagetelco":http://www.villagetelco.org uses batmand in the VT firmware version of the Mesh-Potato device for VOIP mesh networks. (There is a second firmware for the Mesh-Potato named SECN, which uses batman-adv). The "Serval project": http://www.servalproject.org uses batmand on smartphones. h2. BMX

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/FAQ (5f9c81d3)
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 5f9c81d37b42e517a98229355285b85cefb873e7 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Nov 21 08:01:33 2011 +0000 doc: open-mesh/FAQ >--------------------------------------------------------------- 5f9c81d37b42e517a98229355285b85cefb873e7 open-mesh/FAQ.textile | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/open-mesh/FAQ.textile b/open-mesh/FAQ.textile index 30f1a1c4..ac9fca85 100644 --- a/open-mesh/FAQ.textile +++ b/open-mesh/FAQ.textile @@ -27,6 +27,10 @@ h2. Can batman-adv run on interfaces in AP / Station / etc mode ? batman-adv doesn't know anything about stuff below the ethernet interface. So you could also use it over layer 2 ethernet tunnels, wifi ap, wifi sta, wifi adhoc, ethernet or even write a virtual interface which prints everything on paper and scans the paper on the remote machine (but you should be fast or increase the ogm interval). +h2. How can I connect non-mesh clients to my batman-adv network ? + +The [[batman-adv:Quick-start-guide|batman-adv quick-start-guide]] explains how to bridge your standard AP / Ethernet interfaces with bat0 which can be problematic if you only possess one WiFi card. In these cases it might be desirable to run adhoc mode and AP mode at the same time. Fortunately, some WiFi chips / drivers support a so-called "multi VAP" (virtual AP) or "multi SSID" mode to have multiple WiFi networks on the same WiFi interface. + h2. Why does batman need so much time to detect a "dead" node ? Or: Why can I see a node in the originator table a long time after it died ?

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (5dd308df)
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 5dd308df05fb4463310f6fe46b1de787266083a5 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Wed Nov 30 13:32:48 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 5dd308df05fb4463310f6fe46b1de787266083a5 open-mesh/BranchesExplained.textile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 6c9f8bc0..438f7811 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -15,6 +15,8 @@ h2. batmand Historically, the first implementation of the B.A.T.M.A.N. routing protocol was a user space daemon named batmand. Batmand operates on layer 3 (IP layer) of the OSI model by altering the routing table and offers everything you would expect from a standard routing daemon. Almost all real-world implementations of mesh routing algorithms have started on layer 3 - and most of them still work exclusively on layer 3 today. Check our [[UserDocs|docs]] section if you want to learn more about is capabilities. +Note: batmand has not been developed further for a few years, but is still actively used in quite a few projects. Therefore, sources and documentation are still available. Most of the active development today is performed on batman-adv. + h2. BMX

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/NetworkingTechnologies (8f00e7fc)
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 8f00e7fc5421cf876579ef36a741822340604f70 Author: Denis Carikli <GNUtoo(a)no-log.org> Date: Fri Nov 18 19:53:24 2011 +0000 doc: open-mesh/NetworkingTechnologies >--------------------------------------------------------------- 8f00e7fc5421cf876579ef36a741822340604f70 open-mesh/NetworkingTechnologies.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/NetworkingTechnologies.textile b/open-mesh/NetworkingTechnologies.textile index 66535545..d4483586 100644 --- a/open-mesh/NetworkingTechnologies.textile +++ b/open-mesh/NetworkingTechnologies.textile @@ -12,7 +12,7 @@ Let's say you have 3 devices A,B and C connected that way: A<->B<->C with: * C being out of the range of A * A and B being in range * B and C being in range -* A,B,C having the same SSID(it's called BSSID in IBSS networks) +* A,B,C having the same SSID (it's called BSSID in IBSS networks) Batmand will simply route the packets from A to C

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/NetworkingTechnologies (919d8ccf)
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 919d8ccf11a0020f34e1ee9479718ae4f881e7ad Author: Denis Carikli <GNUtoo(a)no-log.org> Date: Fri Nov 18 20:42:29 2011 +0000 doc: open-mesh/NetworkingTechnologies >--------------------------------------------------------------- 919d8ccf11a0020f34e1ee9479718ae4f881e7ad open-mesh/NetworkingTechnologies.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/NetworkingTechnologies.textile b/open-mesh/NetworkingTechnologies.textile index ec7b7deb..fc95d282 100644 --- a/open-mesh/NetworkingTechnologies.textile +++ b/open-mesh/NetworkingTechnologies.textile @@ -20,7 +20,7 @@ Given the nature of IBSS networks, B doesn't need to have 2 wifi cards(one is en h2. Batman-adv -Unlike batmand, batman-advanced is not limited to IBSS networks but can run on a variety of networks. +Batmand can run on top of all ethernet-compatible networks.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/NetworkingTechnologies (aef7da3e)
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 aef7da3ed0db9912de4eb7fa76b5d2fffe2490df Author: Denis Carikli <GNUtoo(a)no-log.org> Date: Fri Nov 18 19:56:07 2011 +0000 doc: open-mesh/NetworkingTechnologies >--------------------------------------------------------------- aef7da3ed0db9912de4eb7fa76b5d2fffe2490df open-mesh/NetworkingTechnologies.textile | 1 + 1 file changed, 1 insertion(+) diff --git a/open-mesh/NetworkingTechnologies.textile b/open-mesh/NetworkingTechnologies.textile index 59553cdd..ec7b7deb 100644 --- a/open-mesh/NetworkingTechnologies.textile +++ b/open-mesh/NetworkingTechnologies.textile @@ -15,6 +15,7 @@ Let's say you have 3 devices A,B and C connected that way: A<->B<->C with: * A,B,C having the same SSID (it's called BSSID in IBSS networks) Batmand will simply route the packets from A to C. + Given the nature of IBSS networks, B doesn't need to have 2 wifi cards(one is enough), however A,B,C need to have the same BSSID. h2. Batman-adv

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/NetworkingTechnologies (c87f2419)
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 c87f241992167559d30b763fcb390ec0ff7a2b2c Author: Denis Carikli <GNUtoo(a)no-log.org> Date: Fri Nov 18 19:50:50 2011 +0000 doc: open-mesh/NetworkingTechnologies >--------------------------------------------------------------- c87f241992167559d30b763fcb390ec0ff7a2b2c open-mesh/NetworkingTechnologies.textile | 1 + 1 file changed, 1 insertion(+) diff --git a/open-mesh/NetworkingTechnologies.textile b/open-mesh/NetworkingTechnologies.textile index 2f008ccd..9f08db03 100644 --- a/open-mesh/NetworkingTechnologies.textile +++ b/open-mesh/NetworkingTechnologies.textile @@ -13,5 +13,6 @@ Let's say you have 3 devices A,B and C connected that way: A<->B<->C with: * A and B being in range * B and C being in range * A,B,C having the same SSID(it's called BSSID in IBSS networks) + Batmand will simply route the packets from A to C

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/NetworkingTechnologies (61488410)
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 614884102950edaa54ba68d71795192166687746 Author: Denis Carikli <GNUtoo(a)no-log.org> Date: Fri Nov 18 19:55:56 2011 +0000 doc: open-mesh/NetworkingTechnologies >--------------------------------------------------------------- 614884102950edaa54ba68d71795192166687746 open-mesh/NetworkingTechnologies.textile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/open-mesh/NetworkingTechnologies.textile b/open-mesh/NetworkingTechnologies.textile index d4483586..59553cdd 100644 --- a/open-mesh/NetworkingTechnologies.textile +++ b/open-mesh/NetworkingTechnologies.textile @@ -14,7 +14,8 @@ Let's say you have 3 devices A,B and C connected that way: A<->B<->C with: * B and C being in range * A,B,C having the same SSID (it's called BSSID in IBSS networks) -Batmand will simply route the packets from A to C +Batmand will simply route the packets from A to C. +Given the nature of IBSS networks, B doesn't need to have 2 wifi cards(one is enough), however A,B,C need to have the same BSSID. h2. Batman-adv

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/NetworkingTechnologies (a95aee81)
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 a95aee81e8ea8462cfcc150149c6209ea95741db Author: Denis Carikli <GNUtoo(a)no-log.org> Date: Fri Nov 18 20:42:41 2011 +0000 doc: open-mesh/NetworkingTechnologies >--------------------------------------------------------------- a95aee81e8ea8462cfcc150149c6209ea95741db open-mesh/NetworkingTechnologies.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/NetworkingTechnologies.textile b/open-mesh/NetworkingTechnologies.textile index fc95d282..58ecf621 100644 --- a/open-mesh/NetworkingTechnologies.textile +++ b/open-mesh/NetworkingTechnologies.textile @@ -20,7 +20,7 @@ Given the nature of IBSS networks, B doesn't need to have 2 wifi cards(one is en h2. Batman-adv -Batmand can run on top of all ethernet-compatible networks. +Batman-adv can run on top of all ethernet-compatible networks.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017