Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
>---------------------------------------------------------------
commit 8c46bc4a8ac395183c8f1cac38d7f530895291ec
Author: Marek Lindner <mareklindner(a)neomailbox.ch>
Date: Tue Nov 30 01:36:15 2010 +0000
doc: batman-adv/Wiki
>---------------------------------------------------------------
8c46bc4a8ac395183c8f1cac38d7f530895291ec
batman-adv/Wiki.textile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/batman-adv/Wiki.textile b/batman-adv/Wiki.textile
index 7ac14a08..0e26e004 100644
--- a/batman-adv/Wiki.textile
+++ b/batman-adv/Wiki.textile
@@ -1,4 +1,3 @@
-
= B.A.T.M.A.N. advanced =
{{{
@@ -8,7 +7,7 @@ B.A.T.M.A.N. advanced (often referenced as batman-adv) is an implementation of t
=== Layer 2 ? ===
-Most other wireless routing protocol implementations (e.g. the batman daemon) operate on layer 3 which means they exchange routing information by sending UDP packets and bring their routing decision into effect by manipulating the kernel routing table. Batman-adv operates entirely on ISO/OSI Layer 2 - not only the routing information is transported using raw ethernet frames but also the data traffic is handled by batman-adv. It encapsulates and forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and unaware of the network's topology as well as unaffected by any network changes.
+Most other wireless routing protocol implementations (e.g. the batman daemon) operate on layer 3 which means they exchange routing information by sending UDP packets and bring their routing decision into effect by manipulating the kernel routing table. Batman-adv operates entirely on ISO/OSI Layer 2 - not only the routing information is transported using raw ethernet frames but also the data traffic is handled by batman-adv. It encapsulates and forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.
This design bears some interesting characteristics:
* network-layer agnostic - you can run whatever you wish on top of batman-adv: IPv4, IPv6, DHCP, IPX ..