Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit a5695428b2528d68867889ac954814327d6ed218 Author: Marek Lindner mareklindner@neomailbox.ch Date: Sat Aug 13 20:32:28 2011 +0000
doc: open-mesh/BranchesExplained
a5695428b2528d68867889ac954814327d6ed218 open-mesh/BranchesExplained.textile | 1 + 1 file changed, 1 insertion(+)
diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 9db1c2b7..07bb5223 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -16,6 +16,7 @@ h2. batmand
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.
h2. BMX