commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

Start a nNew thread

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (540ea2f0)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (fbeff918)
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 fbeff91853b843ac54552e02f6d92aa210f71b18 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Wed Nov 30 13:35:34 2011 +0000 doc: open-mesh/Download >--------------------------------------------------------------- fbeff91853b843ac54552e02f6d92aa210f71b18 open-mesh/Download.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index 77d75467..3c31c1f7 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -10,7 +10,7 @@ h2. Download Released Source Code * The latest version of [[batman-adv:Wiki|batman-adv]] is "batman-adv-2011.4.0.tar.gz":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.4.0.tar.gz "md5":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.4.0.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.4.0.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.4.0.tar.gz.asc * The latest version of batctl (management and control tool for batman-adv) is "batctl-2011.4.0.tar.gz":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.4.0.tar.gz "md5":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.4.0.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.4.0.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.4.0.tar.gz.asc -* The latest stable version of batmand ([[open-mesh:BranchesExplained#batmand|deprecated]]) is "batman-0.3.2.tar.gz":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz "md5":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.asc +* The latest stable version of batmand ([[open-mesh:BranchesExplained#batmand|unmaintained]]) is "batman-0.3.2.tar.gz":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz "md5":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.asc * The latest version of the vis server for the batmand (package not needed for batman-adv) is "vis-0.3.2.tar.gz":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz "md5":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.asc If you are wondering whether batman-adv or batmand might suit your setup better, have a look at [[batman-adv:Wiki|this page]]. Please note that the development is focusing on batman-adv at the moment.

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Using-batctl (c4701c26)
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 c4701c26693645482111dcf78173962d2db2650f Author: Martin Hundebøll <martin(a)hundeboll.net> Date: Fri Dec 2 16:54:06 2011 +0000 doc: batman-adv/Using-batctl >--------------------------------------------------------------- c4701c26693645482111dcf78173962d2db2650f batman-adv/Using-batctl.textile | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/batman-adv/Using-batctl.textile b/batman-adv/Using-batctl.textile index 7a4a8ce5..6060ea22 100644 --- a/batman-adv/Using-batctl.textile +++ b/batman-adv/Using-batctl.textile @@ -13,7 +13,12 @@ A quick overview of the config options available with batctl: h2. Using batctl for debugging -batctl offers a great deal of tools for monitoring the state of your mesh node/network. For many of the features to be available, you must compile your kernel with debugfs (it usually is by default) and mount your debugfs: +batctl offers a great deal of tools for monitoring the state of your mesh node/network: +* Ping and traceroute nodes based on their MAC-addresses. +* Parse logfiles to discover routing loops. +* Retrieve live information from the batman-adv module. + +To retrieve information, you must compile your kernel with debugfs (it usually is by default) and mount your debugfs: <pre> mount -t debugfs none /sys/kernel/debug </pre> @@ -22,4 +27,4 @@ With debugfs mounted, you can use batctl to, among other, seeing the following: * A list of other mesh nodes in the network (originators). * Lists of none-mesh nodes connected to the network (clients or neighbors). * A list of available gateways in the network. -* Log messages from the batman-adv module (if debug \ No newline at end of file +* Log messages from the batman-adv module (if debug is compiled into the module). \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (94cbd86e)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Using-batctl (a831581b)
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 a831581bb5549b57074f053b41e5ddc6e6b031a2 Author: Martin Hundebøll <martin(a)hundeboll.net> Date: Fri Dec 2 16:43:18 2011 +0000 doc: batman-adv/Using-batctl >--------------------------------------------------------------- a831581bb5549b57074f053b41e5ddc6e6b031a2 batman-adv/Using-batctl.textile | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/batman-adv/Using-batctl.textile b/batman-adv/Using-batctl.textile new file mode 100644 index 00000000..7a4a8ce5 --- /dev/null +++ b/batman-adv/Using-batctl.textile @@ -0,0 +1,25 @@ +h1. Using batctl + +Batctl is the configuration and debugging tool for batman-adv. It is thoroughly documented in its man page, so please refer to "man batctl" on your system or "this online version":http://downloads.open-mesh.org/batman/manpages/batctl.8.html . + +h2. Using batctl for configuration + +All configuration of batman-adv is done in the virtual filesystem _sysfs_ and batctl is merely an convenient interface to this. + +A quick overview of the config options available with batctl: +* Add and remove interfaces to the mesh network. +* Set or change parameters of batman-adv module. +* Enable or disable features of batman-adv. (e.g. gateway announcements). + +h2. Using batctl for debugging + +batctl offers a great deal of tools for monitoring the state of your mesh node/network. For many of the features to be available, you must compile your kernel with debugfs (it usually is by default) and mount your debugfs: +<pre> +mount -t debugfs none /sys/kernel/debug +</pre> + +With debugfs mounted, you can use batctl to, among other, seeing the following: +* A list of other mesh nodes in the network (originators). +* Lists of none-mesh nodes connected to the network (clients or neighbors). +* A list of available gateways in the network. +* Log messages from the batman-adv module (if debug \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (5c5ec5ef)
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 5c5ec5ef26175c86005d7a3bbc5c42bce3264964 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Mon Nov 28 17:47:00 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 5c5ec5ef26175c86005d7a3bbc5c42bce3264964 open-mesh/BranchesExplained.textile | 1 - 1 file changed, 1 deletion(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 8d9eb2e8..6c9f8bc0 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -15,7 +15,6 @@ 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. h2. BMX

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (28157ee8)
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 28157ee8d8eb1b30f75804cd3bc558991785b168 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Sun Nov 27 17:20:34 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 28157ee8d8eb1b30f75804cd3bc558991785b168 open-mesh/BranchesExplained.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 1282109d..8d9eb2e8 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -15,7 +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. +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 (40a1657b)
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 40a1657b83f84b8bcbb73d5afeb277b3b82ee206 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Sun Nov 27 17:19:44 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 40a1657b83f84b8bcbb73d5afeb277b3b82ee206 open-mesh/BranchesExplained.textile | 1 + 1 file changed, 1 insertion(+) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 0bf98d80..1282109d 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -16,6 +16,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. + h2. BMX

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (739a625b)
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 739a625bb15b618b151f96c73797d3f2be2a770d Author: elektra wagenrad <onelektra(a)gmx.net> Date: Sun Nov 27 17:17:44 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 739a625bb15b618b151f96c73797d3f2be2a770d open-mesh/BranchesExplained.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 59745484..a5f0abb2 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -13,9 +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. +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 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. +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. h2. BMX

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017