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

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

commit b320a9090b5fcf2eb0d88a9d7962c70d6daec9e6 Author: Sven Eckelmann sven@narfation.org Date: Sun Mar 27 00:30:20 2011 +0000

doc: open-mesh/BranchesExplained

b320a9090b5fcf2eb0d88a9d7962c70d6daec9e6 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 9d986536..ebc08298 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -38,7 +38,7 @@ Early 2007 some developers started experimenting with the idea of routing on lay

However, the virtual interface in userspace imposed a significant overhead for low-end wireless access points which led to a re-implementation as a kernel module. The batman-adv userspace daemon has been removed, so today "batman-adv" refers to the kernel module only. Currently, most of the development happens around batman-adv which is part of the official Linux kernel since 2.6.38.

-To understand the implications of routing on layer 2, the [[batman-adv|batman-adv page]] should be a good starting point Further documentation is available in our [[UserDocs|docs]] section. +To understand the implications of routing on layer 2, the [[batman-adv:Wiki|batman-adv page]] should be a good starting point Further documentation is available in our [[UserDocs|docs]] section.