Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 5dd308df05fb4463310f6fe46b1de787266083a5 Author: Marek Lindner mareklindner@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