Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit 5c5ec5ef26175c86005d7a3bbc5c42bce3264964 Author: elektra wagenrad onelektra@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