commits December 2017

commits@lists.open-mesh.org

1 participants
242 discussions

[doc] batman-adv-doc, master: update echo cancellation 2 picture (8076d8b0)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit 8076d8b0cb2e939b471bdbf093ce05f60669298f Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Sat Apr 11 01:48:59 2009 +0200 update echo cancellation 2 picture >--------------------------------------------------------------- 8076d8b0cb2e939b471bdbf093ce05f60669298f images/echo_cancel2.dia | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/images/echo_cancel2.dia b/images/echo_cancel2.dia index 59dedd14..b1859496 100644 --- a/images/echo_cancel2.dia +++ b/images/echo_cancel2.dia @@ -185,14 +185,14 @@ <dia:point val="7,-4"/> </dia:attribute> <dia:attribute name="obj_bb"> - <dia:rectangle val="7,-4.6775;13.48,-1.505"/> + <dia:rectangle val="7,-4.69875;14.4588,-1.4625"/> </dia:attribute> <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> <dia:string>#step1: source = A -old originator = A#</dia:string> +previous sender = A#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="0" name="Helvetica"/> @@ -281,14 +281,14 @@ old originator = A#</dia:string> <dia:point val="18,-4"/> </dia:attribute> <dia:attribute name="obj_bb"> - <dia:rectangle val="18,-4.6775;24.015,-1.505"/> + <dia:rectangle val="18,-4.69875;25.4587,-1.4625"/> </dia:attribute> <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> <dia:string>#step 2: source = B -old originator=A#</dia:string> +previous sender = A#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="0" name="Helvetica"/> @@ -316,16 +316,17 @@ old originator=A#</dia:string> <dia:point val="7,7"/> </dia:attribute> <dia:attribute name="obj_bb"> - <dia:rectangle val="7,6.358;15.72,11.596"/> + <dia:rectangle val="7,6.33021;14.9744,12.6229"/> </dia:attribute> <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> <dia:string>#step 2: source = B -old originator = A +previous sender = A -A will ignore this packet#</dia:string> +A will not rebroadcast +this packet#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="0" name="Helvetica"/> @@ -353,16 +354,17 @@ A will ignore this packet#</dia:string> <dia:point val="19,7"/> </dia:attribute> <dia:attribute name="obj_bb"> - <dia:rectangle val="19,6.358;27.72,11.596"/> + <dia:rectangle val="19,6.33021;26.9744,12.6229"/> </dia:attribute> <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> <dia:string>#step 3: source = C -old originator = B +previous sender = B -B will ignore this packet#</dia:string> +B will not rebroadcast +this packet#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="0" name="Helvetica"/> @@ -390,14 +392,14 @@ B will ignore this packet#</dia:string> <dia:point val="28,-4"/> </dia:attribute> <dia:attribute name="obj_bb"> - <dia:rectangle val="28,-4.6775;34.48,-1.505"/> + <dia:rectangle val="28,-4.69875;35.4588,-1.4625"/> </dia:attribute> <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> <dia:string>#step 3: source = C -old originator = B#</dia:string> +previous sender = B#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="0" name="Helvetica"/>

1 0

[doc] batman-adv-doc, master: remove deprecated hop penalty section (dbc0c083)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit dbc0c083ce4b1a9639ba7b075f49da89df1694bf Author: Marek Lindner <lindner_marek(a)yahoo.de> Date: Sat Apr 11 08:12:48 2009 +0800 remove deprecated hop penalty section >--------------------------------------------------------------- dbc0c083ce4b1a9639ba7b075f49da89df1694bf batman_iv.docbook | 47 ----------------------------------------------- 1 file changed, 47 deletions(-) diff --git a/batman_iv.docbook b/batman_iv.docbook index 4b9afe04..d98f5cbb 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -324,53 +324,6 @@ <para> Even in more sophisticated scenarios with more nodes/hops this concept successfully reduces the packets. It ensures that packet only travels paths which did not see this OGM before. </para> -<para> - In certain cases B.A.T.M.A.N. IV is unable to detect the 'real' source of an OGM which may lead to temporary routing loops. The following section is going to illustrate the issue and how the echo cancellation addresses it using an Ethernet network as example for the sake of simplicity. WiFi and other mediums are less susceptible as Ethernet but still affected. -</para> -<para> - Example: The node S (source) has a WiFi connection towards node A but no link to node B at all. Node A and node B are connected via Ethernet. We assume the Ethernet connection to be perfect (no packet loss) whereas the WiFi connection suffers from occasional collisions and interferences. -</para> -<para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/hop_penalty3.eps" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/hop_penalty3.png" format="PNG" /> </imageobject> - <textobject> <phrase>example topology</phrase> </textobject> - </inlinemediaobject> -</para> -<para> - Whenever node A receives a packet via the WiFi connection it will rebroadcast the information on the Ethernet to inform neighbor nodes about the existance of the source node. Node B receives the broadcast and parses the packet before rebroadcasting it. At that point node A will receive that very packet again. -</para> -<para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/hop_penalty4.eps" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/hop_penalty4.png" format="PNG" /> </imageobject> - <textobject> <phrase>packet hops</phrase> </textobject> - </inlinemediaobject> -</para> -<para> - B.A.T.M.A.N. III would have dropped the packet at this point. It has a duplicate packet detection based on sequence numbers only. The sequence number is known, hence the packet dropped (the fastest packet wins). In asymetric environments this may lead to suboptimal routing decisions. Therefore B.A.T.M.A.N. IV interprets the arrival of this packet as second path towards the originator. This path transmits the packet slower (due to more hops for example) but but may offer a better transmit quality. Duplicate sequence numbers are dropped if they arrive via the same neighbor. -</para> -<para> - On a lossy medium the TQ value is decreased while travelling from hop to hop (see asymetric link handling). The Ethernet connection does not suffer from packet loss which results in not decreasing the TQ value at all. Node A has 2 possible routes towards the originator: The node S itself and node B (both will advertise the same TQ value). -</para> -<para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/hop_penalty5.eps" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/hop_penalty5.png" format="PNG" /> </imageobject> - <textobject> <phrase>route candidates</phrase> </textobject> - </inlinemediaobject> -</para> -<para> - As B.A.T.M.A.N. IV values TQ and fastest packet the node A's route will point towards the node S. Once the WiFi link quality drops (for a few moments due to some collisions) the TQ value from the node S will drop. At that point the B.A.T.M.A.N. IV node A will change its route towards node B which offers a better TQ value. Node A and node B will send packets forth and back in a loop. -</para> -<para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/hop_penalty6.eps" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/hop_penalty6.png" format="PNG" /> </imageobject> - <textobject> <phrase>applied hop penalty</phrase> </textobject> - </inlinemediaobject> - -</para> </sect2> <sect2 id="batman4_tq_hop_penalty">

1 0

[doc] batman-adv-doc, master: update asym_link2 to be more clear about the used TQ (e27c218c)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit e27c218c536795122308acfe218e26ffad62ce51 Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Sat Apr 11 17:50:17 2009 +0200 update asym_link2 to be more clear about the used TQ >--------------------------------------------------------------- e27c218c536795122308acfe218e26ffad62ce51 images/asym_link2.dia | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/images/asym_link2.dia b/images/asym_link2.dia index 5df51f22..b170d6e7 100644 --- a/images/asym_link2.dia +++ b/images/asym_link2.dia @@ -239,15 +239,15 @@ </dia:object> <dia:object type="Standard - Text" version="1" id="O6"> <dia:attribute name="obj_pos"> - <dia:point val="6.58206,-0.884177"/> + <dia:point val="3.03206,-0.834177"/> </dia:attribute> <dia:attribute name="obj_bb"> - <dia:rectangle val="6.58206,-1.56168;8.20456,-0.389177"/> + <dia:rectangle val="3.03206,-1.53293;12.7883,-0.296677"/> </dia:attribute> <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> - <dia:string>#95%#</dia:string> + <dia:string>#24.75 (incoming TQ=95%)#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="0" name="Helvetica"/> @@ -256,7 +256,7 @@ <dia:real val="1"/> </dia:attribute> <dia:attribute name="pos"> - <dia:point val="6.58206,-0.884177"/> + <dia:point val="3.03206,-0.834177"/> </dia:attribute> <dia:attribute name="color"> <dia:color val="#000000"/>

1 0

[doc] batman-adv-doc,master: add % to figure (7a7338e6)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit 7a7338e6b5492d7decd81ced5539a64fb8f135bd Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Sat Apr 11 18:30:38 2009 +0200 add % to figure >--------------------------------------------------------------- 7a7338e6b5492d7decd81ced5539a64fb8f135bd images/asym_link2.dia | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/images/asym_link2.dia b/images/asym_link2.dia index b170d6e7..fbebff7a 100644 --- a/images/asym_link2.dia +++ b/images/asym_link2.dia @@ -242,12 +242,12 @@ <dia:point val="3.03206,-0.834177"/> </dia:attribute> <dia:attribute name="obj_bb"> - <dia:rectangle val="3.03206,-1.53293;12.7883,-0.296677"/> + <dia:rectangle val="3.03206,-1.53293;13.4808,-0.296677"/> </dia:attribute> <dia:attribute name="text"> <dia:composite type="text"> <dia:attribute name="string"> - <dia:string>#24.75 (incoming TQ=95%)#</dia:string> + <dia:string>#24.75% (incoming TQ=95%)#</dia:string> </dia:attribute> <dia:attribute name="font"> <dia:font family="sans" style="0" name="Helvetica"/>

1 0

[doc] batman-adv-doc, master: update asymetry penalty section, add formula in text (a4ea3344)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit a4ea33448b5daa130f5ace9f0d4b9c178ca3d171 Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Sat Apr 11 18:55:50 2009 +0200 update asymetry penalty section, add formula in text >--------------------------------------------------------------- a4ea33448b5daa130f5ace9f0d4b9c178ca3d171 batman_iv.docbook | 12 ++++++++++-- images/Makefile | 2 +- images/{tq_prop_calc.tex => asym_penalty_formula.tex} | 2 +- 3 files changed, 12 insertions(+), 4 deletions(-) diff --git a/batman_iv.docbook b/batman_iv.docbook index d98f5cbb..a73483fd 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -272,7 +272,15 @@ </inlinemediaobject> </para> <para> - Thus B.A.T.M.A.N. IV needs to penalize links that have have a poor receiving link quality. To avoid a simple hysteresis which completely turns on or off a link B.A.T.M.A.N. IV uses a mathematical function to give the receiving link quality stronger negative impact the weaker the link becomes. + Thus B.A.T.M.A.N. IV needs to penalize links that have have a poor receiving link quality. To avoid a simple hysteresis which completely turns on or off a link, B.A.T.M.A.N. IV uses the function + <inlinemediaobject> + <imageobject> <imagedata fileref="images/asym_penalty_formula.eps" format="EPS"/> </imageobject> + <imageobject> <imagedata fileref="images/asym_penalty_formula.png" format="PNG" /> </imageobject> + <textobject> <phrase>compute the asymetry penalty factor</phrase> </textobject> + </inlinemediaobject> + to weight the penalty for the receiving link quality. As visible in the plot below, small packet + loss will influence the link rating only a little, while huge packet loss will still have a severe + influence TQ. </para> <para> <inlinemediaobject> @@ -282,7 +290,7 @@ </inlinemediaobject> </para> <para> - This obtained value is calculated into the TQ before it gets rebroadcasted. Neighboring nodes can weight the routing decision based on this information. In some situations the weak link is the only link available, so you want to use it, whereas in other cases better connections may exist. + This obtained value is multiplicated on the TQ before it gets rebroadcasted. Neighboring nodes can weight the routing decision based on this information. In some situations the weak link is the only link available, so you want to use it, whereas in other cases better connections may exist. </para> <para> <inlinemediaobject> diff --git a/images/Makefile b/images/Makefile index 139f6e52..d003929f 100644 --- a/images/Makefile +++ b/images/Makefile @@ -6,7 +6,7 @@ DIA_IMAGES=asymetry.dia tq.dia eq.dia eq_alt1.dia eq_alt2.dia eq_alt3.dia rq.dia echo_cancel1.dia echo_cancel2.dia \ tq_prop_best1.dia tq_prop_best2.dia tq_prop_best3.dia \ announce_networks.dia multiple_announces.dia multiple_clients.dia -TEX_IMAGES=compute_tq.tex tq_prop_calc.tex +TEX_IMAGES=compute_tq.tex tq_prop_calc.tex asym_penalty_formula.tex PNG_IMAGES= $(DIA_IMAGES:.dia=.png) PNG_IMAGES+=$(GP_IMAGES:.gp=.png) PNG_IMAGES+=$(TEX_IMAGES:.tex=.png) diff --git a/images/tq_prop_calc.tex b/images/asym_penalty_formula.tex similarity index 65% copy from images/tq_prop_calc.tex copy to images/asym_penalty_formula.tex index 23b71086..577590b8 100644 --- a/images/tq_prop_calc.tex +++ b/images/asym_penalty_formula.tex @@ -1,6 +1,6 @@ \documentclass{article} \pagestyle{empty} \begin{document} -$TQ = TQ_{incoming} * TQ_{local}$ +$f_{asym} = (100\% - (100\% - {RQ})^3)$ \end{document}

1 0

[doc] batman-adv-doc, master: multiple interfaces added (b77a9ee1)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit b77a9ee1462a6f143763dd87a178e7923d6f7f23 Author: Marek Lindner <lindner_marek(a)yahoo.de> Date: Sun Apr 12 01:02:56 2009 +0800 multiple interfaces added >--------------------------------------------------------------- b77a9ee1462a6f143763dd87a178e7923d6f7f23 batman_iv.docbook | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/batman_iv.docbook b/batman_iv.docbook index d98f5cbb..04e56828 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -447,14 +447,20 @@ </para> </sect2> - <sect2 id="multiple_interfaces"> +<sect2 id="multiple_interfaces"> <title>Multiple Interfaces</title> <para> -TODO Explain multiple interfaces, which interface sends which OGM by which TTL, and why. -(Maybe move this section somewhere else ... ) - -==> why explaining this in this document ? I would refer them to the RFC because this did not change with IV. - </para> + In order to support nodes with several network interfaces B.A.T.M.A.N. needs to detect which link connects to what interface. As every incoming packet is rebroadcasted via all existing interfaces B.A.T.M.A.N. IV needs to use a flag (direct link flag) to distinguish between real connections and rebroadcasts. +</para> +<para> + The detection process: Node A emits an OGM without any enabled flags. The neighbor B receives the message and checks whether the UDP sender address and the originator address are equal. If so it will rebroadcasting the OGM with the direct link flag enabled otherwise the flags are not changed. Once node A receives this rebroadcast of its own OGM it recognizes this neighbor as single-hop neighbor due to the existing direct link flag. If node A received this package via the same interface it was sent out (incoming interface address equals originator address) node A will accept this package and increase the the Echo Quality (EQ) packet count. Its ignored otherwise. +</para> +<para> + Examples: Node A hast 2 interfaces and broadcasts the OGM of one interface over both interfaces to make it known in the mesh cloud. Node B also has 2 interfaces and receives this broadcast via both. The OGM that orignated via the interface it belongs to is accepted to other one ignored (for further interface detection). +</para> +<para> + Node B will rebroadcast the message over both interfaces as well but only set the direct link interface flag on the packet that leaves the node via the interface the message came in. Node A will ignore the packet without the direct link flag and only counts the OGM that comes in via the interface it left in the first place. +</para> </sect2> </sect1>

1 0

[doc] batman-adv-doc, master: Merge branch 'master' of gitorious:batman-adv-doc/mainline (1f24245f)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit 1f24245fe76a35d00dd76b7422de006758b76cf0 Merge: b77a9ee1 a4ea3344 Author: Marek Lindner <lindner_marek(a)yahoo.de> Date: Sun Apr 12 01:03:28 2009 +0800 Merge branch 'master' of gitorious:batman-adv-doc/mainline >--------------------------------------------------------------- 1f24245fe76a35d00dd76b7422de006758b76cf0 batman_iv.docbook | 12 ++++++++++-- images/Makefile | 2 +- images/asym_link2.dia | 8 ++++---- images/{tq_prop_calc.tex => asym_penalty_formula.tex} | 2 +- 4 files changed, 16 insertions(+), 8 deletions(-)

1 0

[doc] batman-adv-doc,master: more caps (bb4b5ee2)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit bb4b5ee236b292bb5678565c91e16422f717146b Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Fri Apr 10 13:35:14 2009 +0200 more caps >--------------------------------------------------------------- bb4b5ee236b292bb5678565c91e16422f717146b batman_iv.docbook | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/batman_iv.docbook b/batman_iv.docbook index f98f169c..0b47682f 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -73,7 +73,7 @@ <title>The B.A.T.M.A.N. IV Originator Message Format</title> <para> <table> - <title>B.A.T.M.A.N. IV (layer 3) Packet Format</title> + <title>B.A.T.M.A.N. IV (Layer 3) Packet Format</title> <tgroup cols="5"> <colspec colnum="1" colname="colB" colwidth="1*"/> <colspec colnum="2" colname="col0" colwidth="1*"/> @@ -396,7 +396,7 @@ </para> <para> <table> - <title>HNA (layer 3) Message Format</title> + <title>HNA (Layer 3) Message Format</title> <tgroup cols="5"> <colspec colnum="1" colname="colB" colwidth="1*"/> <colspec colnum="2" colname="col0" colwidth="1*"/> @@ -430,7 +430,7 @@ </para> <para> <table> - <title>Example B.A.T.M.A.N. IV (layer 3) Aggregated Packet</title> + <title>Example B.A.T.M.A.N. IV (Layer 3) Aggregated Packet</title> <tgroup cols="5"> <colspec colnum="1" colname="colB" colwidth="1*"/> <colspec colnum="2" colname="col0" colwidth="1*"/>

1 0

[doc] batman-adv-doc, master: use capital letters in titles (c737c2b1)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit c737c2b113f4c5bba0d62910d4b3ce65ca9d0b90 Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Fri Apr 10 13:33:43 2009 +0200 use capital letters in titles >--------------------------------------------------------------- c737c2b113f4c5bba0d62910d4b3ce65ca9d0b90 batman_adv.docbook | 2 +- batman_iv.docbook | 22 +++++++++++----------- batmand.docbook | 2 +- 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/batman_adv.docbook b/batman_adv.docbook index 70cf8b4d..5c6d600e 100644 --- a/batman_adv.docbook +++ b/batman_adv.docbook @@ -26,7 +26,7 @@ talk Ethernet via raw sockets (SOCK_RAW). </para> <table> - <title>Ethernet embedding</title> + <title>Ethernet Embedding</title> <tgroup cols="9"> <colspec colnum="1" colname="colB" colwidth="1*"/> <colspec colnum="2" colname="col0" colwidth="1*"/> diff --git a/batman_iv.docbook b/batman_iv.docbook index aa2ffd36..f98f169c 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -2,7 +2,7 @@ <chapter id="batman_iv_tq"> <title>B.A.T.M.A.N. IV (TQ) Meshing</title> <sect1 id="batman3"> -<title>B.A.T.M.A.N. III (introduction)</title> +<title>B.A.T.M.A.N. III (Introduction)</title> <para> B.A.T.M.A.N. is a proactive routing protocol for Wireless Ad-hoc Mesh Networks, including (but not limited to) Mobile Ad-hoc Networks @@ -20,7 +20,7 @@ </para> <sect2 id="how_works"> -<title>B.A.T.M.A.N. III (brief overview)</title> +<title>B.A.T.M.A.N. III (Brief Overview)</title> <para> On a regular basis every B.A.T.M.A.N. node broadcasts an originator message (or OGM), thereby informing its link-local neighbors about @@ -70,10 +70,10 @@ To overcome this flaw B.A.T.M.A.N. IV has been enhanced with the Transmit Quality (TQ) algorithm. The following sections are going to outline its design and how it strengthens B.A.T.M.A.N.'s routing capabilities in asymetric environments. </para> <sect2 id="batman4_packet_layout"> -<title>The B.A.T.M.A.N. IV originator message format</title> +<title>The B.A.T.M.A.N. IV Originator Message Format</title> <para> <table> - <title>B.A.T.M.A.N. IV (layer 3) packet format</title> + <title>B.A.T.M.A.N. IV (layer 3) Packet Format</title> <tgroup cols="5"> <colspec colnum="1" colname="colB" colwidth="1*"/> <colspec colnum="2" colname="col0" colwidth="1*"/> @@ -243,7 +243,7 @@ </sect2> <sect2 id="batman4_local_global_tq"> -<title>local TQ vs global TQ</title> +<title>Local TQ vs Global TQ</title> <para> A B.A.T.M.A.N. IV node has to keep track of 2 different TQ values: <orderedlist> @@ -260,7 +260,7 @@ </sect2> <sect2 id="batman4_tq_asymetry"> -<title>Handling asymetric links</title> +<title>Handling Asymetric Links</title> <para> Although the transmit link quality is most important decision factor B.A.T.M.A.N. IV also keeps track of the receiving link quality. On the WiFi layer every unicast packet has to be acknowledged by the neighbor node to approve the transmission. If this neighbor is not able to sucessfully send his ACKs the WiFi layer considers this transmission to be failed and tries to retransmit until it gives up. </para> @@ -294,7 +294,7 @@ </sect2> <sect2 id="batman4_tq_echo_cancellation"> -<title>Echo cancellation</title> +<title>Echo Cancellation</title> <para> B.A.T.M.A.N. IV loosens the strict packet drop policy used by B.A.T.M.A.N. III to make the TQ algorithm work. B.A.T.M.A.N. IV checks for unknown sequence numbers via a specific neighbor whereas B.A.T.M.A.N. III checks for known sequence numbers. If this combination is "new" the OGM will be accepted, processed and rebroadcasted. This may duplicate known information when the message "comes back" due to rebroadcasting (so called echos). In dense areas without heavy packet loss this leads to increased bandwidth and CPU usage. </para> @@ -374,7 +374,7 @@ </sect2> <sect2 id="batman4_tq_hop_penalty"> -<title>Hop penalty</title> +<title>Hop Penalty</title> <para> So far, B.A.T.M.A.N. IV focusses only on the link quality to evaluate paths but not on the number of hops in the path as it is unaware of the topology beyond its horizon. In certain network setups the link quality of the neighbors is very similar whereas the number of hops is not. In these scenarios it is very desirable to choose the shortest path to reduce latency and to safe bandwidth (on wireless mediums). The following section is going to illustrate the issue and how it is going to be addressed using an Ethernet network as example for the sake of simplicity. WiFi and other mediums are less susceptible as Ethernet but still affected. </para> @@ -396,7 +396,7 @@ </para> <para> <table> - <title>HNA (layer 3) message format</title> + <title>HNA (layer 3) Message Format</title> <tgroup cols="5"> <colspec colnum="1" colname="colB" colwidth="1*"/> <colspec colnum="2" colname="col0" colwidth="1*"/> @@ -430,7 +430,7 @@ </para> <para> <table> - <title>example B.A.T.M.A.N. IV (layer 3) aggregated packet</title> + <title>Example B.A.T.M.A.N. IV (layer 3) Aggregated Packet</title> <tgroup cols="5"> <colspec colnum="1" colname="colB" colwidth="1*"/> <colspec colnum="2" colname="col0" colwidth="1*"/> @@ -495,7 +495,7 @@ </sect2> <sect2 id="multiple_interfaces"> -<title>multiple interfaces</title> +<title>Multiple Interfaces</title> <para> TODO Explain multiple interfaces, which interface sends which OGM by which TTL, and why. (Maybe move this section somewhere else ... ) diff --git a/batmand.docbook b/batmand.docbook index e984afd9..9f6c68b1 100644 --- a/batmand.docbook +++ b/batmand.docbook @@ -108,7 +108,7 @@ $ make</userinput></programlisting> 192.168.100.x network, because your parameter is /24. So, if you use different netmask values, then the results are different.</para> <figure> - <title>Two announced networks</title> + <title>Two Announced Networks</title> <mediaobject> <imageobject><imagedata fileref="images/multiple_announces.eps" format="EPS" scale="50" /></imageobject> <imageobject><imagedata fileref="images/multiple_announces.png" format="PNG" /></imageobject>

1 0

[doc] batman-adv-doc, master: asym penalty once again (99548f3e)
by postmaster＠open-mesh.org 14 Dec '17

14 Dec '17

Repository : ssh://git@open-mesh.org/doc On branches: batman-adv-doc,master >--------------------------------------------------------------- commit 99548f3e9b8500a75dfd0e7e106ee7dcbcdadced Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Sat Apr 11 00:32:19 2009 +0200 asym penalty once again >--------------------------------------------------------------- 99548f3e9b8500a75dfd0e7e106ee7dcbcdadced images/asym_penalty.gp | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/images/asym_penalty.gp b/images/asym_penalty.gp index 178c42d8..76bd8392 100644 --- a/images/asym_penalty.gp +++ b/images/asym_penalty.gp @@ -1,17 +1,17 @@ #!/usr/bin/gnuplot -set title "Asymetry Penalty Illustration, assuming incoming TQ = 1.0" -set xlabel "receive quality (RQ)" -set ylabel "rebroadcasted TQ value" -set xrange [0:1] -set yrange [0:1] +set title "asymetry penalty illustration, assuming incoming TQ = 100%" +set xlabel "receive quality (RQ) [%]" +set ylabel "rebroadcasted TQ value [%]" +set xrange [100:0] +set yrange [0:100] set grid set terminal png set output "asym_penalty.png" -plot (1 - (1-x) ** 3) title "asymetry penalty 1 - (1-x)^3" +plot (1 - (1-x/100) ** 3)*100 title "rebroadcasted TQ value" set terminal postscript eps enhanced color solid set output "asym_penalty.eps" -plot (1 - (1-x) ** 3) title "asymetry penalty 1 - (1-x)^3" +plot (1 - (1-x/100) ** 3)*100 title "rebroadcasted TQ value"

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
25
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits December 2017