Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit b3ccfdd6ac779a1fcf3e2ef83d8e4cd508931c3e Author: Linus Lüssing linus.luessing@c0d3.blue Date: Tue Jul 5 01:45:32 2011 +0000
doc: batman-adv/ELP
b3ccfdd6ac779a1fcf3e2ef83d8e4cd508931c3e batman-adv/ELP.textile | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/batman-adv/ELP.textile b/batman-adv/ELP.textile index b8054e11..c863c8d0 100644 --- a/batman-adv/ELP.textile +++ b/batman-adv/ELP.textile @@ -1,5 +1,10 @@ h1. Echo Location Protocol (ELP)
+!http://upload.wikimedia.org/wikipedia/commons/e/e1/Animal_echolocation.svg!:... +_Image Source_: "Petteri Aimonen, Wikimedia Commons":http://en.wikipedia.org/wiki/File:Animal_echolocation.svg + +---- + The B.A.T.M.A.N. protocol originally only used a single message type (called OGM) to determine the link qualities to the direct neighbors and spreading these link quality information through the whole mesh. This procedure is summarized on the [[open-mesh:BATMANConcept|BATMAN concept page]] and explained in details in "the RFC draft":http://tools.ietf.org/html/draft-wunderlich-openmesh-manet-routing-00 published in 2008.
This approach was chosen for its simplicity during the protocol design phase and the implementation. However, it also bears some drawbacks: