commits December 2017

commits@lists.open-mesh.org

1 participants
242 discussions

[doc] batman-adv-doc, master: Distinguish between B.A.T.M.A.N. and batmand (9c87446b)
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 9c87446b528c44f6ee3fc65a167fab0330762b8c Author: Sven Eckelmann <sven.eckelmann(a)gmx.de> Date: Wed Jan 21 20:38:15 2009 +0100 Distinguish between B.A.T.M.A.N. and batmand >--------------------------------------------------------------- 9c87446b528c44f6ee3fc65a167fab0330762b8c batmand_howto.tex | 48 ++++++++++++++++++++++++------------------------ 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/batmand_howto.tex b/batmand_howto.tex index 6fea3eb9..f142a7bb 100644 --- a/batmand_howto.tex +++ b/batmand_howto.tex @@ -71,7 +71,7 @@ \begin{abstract} B.A.T.M.A.N stands for ``better approach to mobile ad hoc networking'', this is a new routing protocol for multi-hop ad-hoc mesh networks. Go to \url{http://www.open-mesh.net} to see more information. -The following document will explain how to install and use the batman daemon. +The following document will explain how to install and use the B.A.T.M.A.N. daemon. \end{abstract} @@ -89,7 +89,7 @@ The following document will explain how to install and use the batman daemon. \item GNU make \item libpthread \end{enumerate} -\item Download the batman daemon code from the website +\item Download the B.A.T.M.A.N. daemon code from the website \url{http://www.open-mesh.net/wiki/Download} \end{itemize} @@ -137,7 +137,7 @@ batmand [options] interface [interface interface] \subsection{DESCRIPTION} -You can start batmand without specifying options, but you have to choose at least one interface batman runs on. +You can start batmand without specifying options, but you have to choose at least one interface batmand runs on. \begin{verbatim} $ batmand eth1 \end{verbatim} @@ -145,16 +145,16 @@ If you have more interfaces, then you just add them behind the first. \begin{verbatim} $ batmand eth1 eth2 eth3 \end{verbatim} -The batman daemon can also run on alias interfaces. Note that we use alias interfaces to separate batman routing protocol and olsr routing protocol. +The B.A.T.M.A.N. daemon can also run on alias interfaces. Note that we use alias interfaces to separate B.A.T.M.A.N. routing protocol and olsr routing protocol. \begin{verbatim} $ batmand eth1:test1 eth2:test2 eth3:test3 \end{verbatim} -Note that the batman daemon will take the ip address and the broadcast address from the given interfaces. +Note that the B.A.T.M.A.N. daemon will take the ip address and the broadcast address from the given interfaces. Note also that you have to check whether your essid, channel or wifi mode is correct or not. \subsubsectionttt{-o originator interval in ms} - Originator means a node transmits broadcast messages (we call them originator message or OGM) to inform the neighboring nodes about its existence. Originator interval is the time to wait after sending one message and before the batman daemon sends the next message. + Originator means a node transmits broadcast messages (we call them originator message or OGM) to inform the neighboring nodes about its existence. Originator interval is the time to wait after sending one message and before the B.A.T.M.A.N. daemon sends the next message. The default value is 1000 ms (1 second). @@ -169,8 +169,8 @@ The debug level can be set to five values. \item[0] debug disabled (default) \item[1] list neighbors \item[2] list gateways - \item[3] observe batman - \item[4] observe batman (very verbose) + \item[3] observe batmand + \item[4] observe batmand (very verbose) \end{description} For example, you can run in normal start: @@ -179,7 +179,7 @@ For example, you can run in normal start: \end{verbatim} \paragraph*{Level 1} -just lists the neighbors in your batman network. +just lists the neighbors in your B.A.T.M.A.N. network. \begin{lstlisting}[basicstyle=\footnotesize, frame=single, columns= flexible] Originator Router (#/128): Potential routers... [B.A.T.M.A.N. 0.2, MainIF/IP: @@ -191,16 +191,16 @@ eth2 105.131.131.175, UT: 0d 0h 3m] \end{lstlisting} \begin{itemize} -\item In the first line, we will see the version of the batman daemon, main interface, main IP, and uptime. +\item In the first line, we will see the version of the B.A.T.M.A.N. daemon, main interface, main IP, and uptime. \item In the first column, we can see those IPs which we can reach. \item In the second column, we can see those IPs which we sent our packets to when we want to reach the IP of the first column. The number in the parenthesis indicates the link quality of the connection and the \verb|#/128| shows the maximum number of packets. -\item In the third column, we can see those IPs which are one hop neighbors and rebroadcasted packets from the originator. The batman daemon will choose the router with the best link quality from the potential router list. +\item In the third column, we can see those IPs which are one hop neighbors and rebroadcasted packets from the originator. The B.A.T.M.A.N. daemon will choose the router with the best link quality from the potential router list. \end{itemize} In this case, 105.131.1.2 is a one hop neighbor of 105.131.131.175, because the 105.131.1.2 is originator, router and potential router at the same time. If 105.131.131.175 wants to exchange data with the 105.131.83.2, then it will sent its packets to the 105.131.1.3, because it is the router for this destination. \paragraph*{Level 2} -just lists gateways in the batman network. +just lists gateways in the B.A.T.M.A.N. network. \begin{lstlisting}[basicstyle=\footnotesize, frame=single, columns= flexible] Gateway Router (#/128) @@ -214,13 +214,13 @@ Gateway Router (#/128) \end{itemize} \paragraph*{Level 3} -has more information about the neighbors, or shows the error message when you have an incorrect command. Note that if there is no neighbor in the batman network, then it will display nothing. +has more information about the neighbors, or shows the error message when you have an incorrect command. Note that if there is no neighbor in the B.A.T.M.A.N. network, then it will display nothing. \paragraph*{Level 4} -has so many information about the batman network, for example, how many packets you sent, and sent to where, or how many packets you got, and received from where etc. +has so many information about the B.A.T.M.A.N. network, for example, how many packets you sent, and sent to where, or how many packets you got, and received from where etc. \subsubsectionttt{-c connect via unix socket} -The batman daemon offers a unix socket interface to which you can connect. First, you have to create a batman daemon on your host, then use -c to connect to its interface. Note you can create as many client sockets as you like. +The B.A.T.M.A.N. daemon offers a unix socket interface to which you can connect. First, you have to create a B.A.T.M.A.N. daemon on your host, then use -c to connect to its interface. Note you can create as many client sockets as you like. \begin{center} \includegraphics[scale=0.5]{multiple_clients} @@ -230,7 +230,7 @@ The batman daemon offers a unix socket interface to which you can connect. First $ batmand eth1 $ batmand -c -d 1 \end{verbatim} - In this case, you ask the daemon to output debug level 1 in your current shell. The batman daemon will update the information after a period of time. + In this case, you ask the daemon to output debug level 1 in your current shell. The B.A.T.M.A.N. daemon will update the information after a period of time. Note that if you use -c flag, then you only can use -d to see the debug level. @@ -267,7 +267,7 @@ You only can set the value in a normal start Note that if you use debug level 3, then you will know whether you succeed setting the gateway class or not. \subsubsectionttt{-r routing class} -Routing class can set to four values, it means this node in the batman network wants to connect the Internet and chooses its internet gateway based on certain criteria: +Routing class can set to four values, it means this node in the B.A.T.M.A.N. network wants to connect the Internet and chooses its internet gateway based on certain criteria: \begin{description} \item[0] set no default route (default) \item[1] use fast internet connection @@ -279,7 +279,7 @@ Routing class can set to four values, it means this node in the batman network w B.A.T.M.A.N tries to find the best available connection by watching the uplinks throughput and the link quality. \paragraph*{Level 2} -B.A.T.M.A.N observes the internet nodes and tries to find out which one is the most reliable. This mode is not implemented yet but will follow in batman 0.3. +B.A.T.M.A.N observes the internet nodes and tries to find out which one is the most reliable. This mode is not implemented yet but will follow in batmand 0.3. \paragraph*{Level 3} B.A.T.M.A.N only compares the link quality of the internet node and chooses the one with the best connection. @@ -287,12 +287,12 @@ B.A.T.M.A.N only compares the link quality of the internet node and chooses the \begin{verbatim} $ batmand -r 3 -d 3 eth1 \end{verbatim} -In this case, the batman daemon will choose the best statistic internet connection for you. Note that if you use debug level 3, then you will know whether you succeeded setting the routing class or not. +In this case, the B.A.T.M.A.N. daemon will choose the best statistic internet connection for you. Note that if you use debug level 3, then you will know whether you succeeded setting the routing class or not. \subsubsectionttt{-p preferred gateway} Set the default gateway by yourself. -Note that you have to use -r to tell batman daemon you want to set the default gateway, because -r will be used if the preferred gateway is not available. +Note that you have to use -r to tell B.A.T.M.A.N. daemon you want to set the default gateway, because -r will be used if the preferred gateway is not available. \begin{verbatim} $ batmand -r 3 -d 3 -p 192.168.1.1 eth1 @@ -306,7 +306,7 @@ In this case, you set 192.168.1.1 as your preferred gateway, so all of your inte \includegraphics[scale=0.8]{announce_networks} \end{center} -If the other nodes in the batman network want to connect to node B after receiving the announce network information form node A, then they will know they can use node A as gateway to reach node B. Now, you know what a announced network is, but executing this command is wrong: +If the other nodes in the B.A.T.M.A.N. network want to connect to node B after receiving the announce network information form node A, then they will know they can use node A as gateway to reach node B. Now, you know what a announced network is, but executing this command is wrong: \begin{verbatim} $ batmand -a 192.168.100.101 eth1 \end{verbatim} @@ -333,7 +333,7 @@ Node A can announce more than one network. To announce two networks execute the Note that node A has to have a route to connect the node or network. \subsubsectionttt{-s visualization server} -Since no topology database is computed by the protocol an additional solution to create topology graphs has been implemented, the Vis-Server. Batman daemons may send their local view about their single hop neighbors to the Vis-server. The Vis-Server collects the information and provides data in a format similar to OLSR's topology information output. Therefore existing solutions to draw topology graphs developed for OLSR can be used to visualize mesh clouds using B.A.T.M.A.N. +Since no topology database is computed by the protocol an additional solution to create topology graphs has been implemented, the Vis-Server. B.A.T.M.A.N. daemons may send their local view about their single hop neighbors to the Vis-server. The Vis-Server collects the information and provides data in a format similar to OLSR's topology information output. Therefore existing solutions to draw topology graphs developed for OLSR can be used to visualize mesh clouds using B.A.T.M.A.N. \section{Reference Links} \begin{itemize} @@ -342,8 +342,8 @@ Since no topology database is computed by the protocol an additional solution to \end{itemize} \section{Troubleshooting} -\subsection{Why the batman daemon doesn't reload the setting after I fixed the main IP?} -You have to restart the batman daemon after you modified any network configuration, otherwise the batman daemon won't use the new settings. +\subsection{Why the B.A.T.M.A.N. daemon doesn't reload the setting after I fixed the main IP?} +You have to restart the B.A.T.M.A.N. daemon after you modified any network configuration, otherwise the B.A.T.M.A.N. daemon won't use the new settings. \begin{verbatim} $ killall batmand $ batmand eth1

1 0

[doc] batman-adv-doc, master: "Reference Links" formatted (88a281e7)
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 88a281e75cb0719fd6050c1295222c3f36910672 Author: Sven Eckelmann <sven.eckelmann(a)gmx.de> Date: Wed Jan 21 20:27:39 2009 +0100 "Reference Links" formatted >--------------------------------------------------------------- 88a281e75cb0719fd6050c1295222c3f36910672 batmand_howto.tex | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/batmand_howto.tex b/batmand_howto.tex index e3118fbe..038e97de 100644 --- a/batmand_howto.tex +++ b/batmand_howto.tex @@ -335,10 +335,11 @@ Note that node A has to have a route to connect the node or network. \subsubsectionttt{-s visualization server} Since no topology database is computed by the protocol an additional solution to create topology graphs has been implemented, the Vis-Server. Batman daemons may send their local view about their single hop neighbors to the Vis-server. The Vis-Server collects the information and provides data in a format similar to OLSR's topology information output. Therefore existing solutions to draw topology graphs developed for OLSR can be used to visualize mesh clouds using B.A.T.M.A.N. -\section{Reference link} -? ? - -http://open mesh.net/ <== B.A.T.M.A.N http://www.olsr.org/ <== OLSR +\section{Reference Links} +\begin{itemize} +\item \url{http://www.open-mesh.net/} +\item \url{http://www.olsr.org/} +\end{itemize} \section{Troubleshooting} \subsection{Why the batman daemon doesn't reload the setting after I fixed the main IP?}

1 0

[doc] batman-adv-doc, master: Abstract formatted (dda3e945)
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 dda3e94550bc5e04fef87dcdf182d00840f8d061 Author: Sven Eckelmann <sven.eckelmann(a)gmx.de> Date: Wed Jan 21 17:34:49 2009 +0100 Abstract formatted >--------------------------------------------------------------- dda3e94550bc5e04fef87dcdf182d00840f8d061 batmand_howto.tex | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/batmand_howto.tex b/batmand_howto.tex index 44c745b3..2de6d60f 100644 --- a/batmand_howto.tex +++ b/batmand_howto.tex @@ -65,8 +65,12 @@ \fussy \begin{document} \maketitle -B.A.T.M.A.N stands for ? better approach to mobile ad hoc networking ?, this is a new routing protocol for multi hop ad hoc mesh networks. Go to http://open mesh.net to see more information. The following document will explain how to install and use the batman daemon. +\begin{abstract} + B.A.T.M.A.N stands for ``better approach to mobile ad hoc networking'', this is a new routing protocol for multi-hop ad-hoc mesh networks. Go to \url{http://www.open-mesh.net} to see more information. + +The following document will explain how to install and use the batman daemon. +\end{abstract} \section{Installing from source} ?

1 0

[doc] batman-adv-doc, master: "Copyright" formatted (fc5d6ae0)
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 fc5d6ae0132a12109bb4fb16935504f121f47b2d Author: Sven Eckelmann <sven.eckelmann(a)gmx.de> Date: Wed Jan 21 20:35:05 2009 +0100 "Copyright" formatted >--------------------------------------------------------------- fc5d6ae0132a12109bb4fb16935504f121f47b2d batmand_howto.tex | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/batmand_howto.tex b/batmand_howto.tex index 1b9c1754..6fea3eb9 100644 --- a/batmand_howto.tex +++ b/batmand_howto.tex @@ -356,6 +356,11 @@ You have to use NAT on your gateway or firewall if you use the -r or -p options \end{verbatim} Note that you don't set the default route by yourself. -This work is licensed under the Creative Commons Attribution Noncommercial Share Alike 3.0 License. To -view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. +\vfill +\section*{Copyright} +\begin{center} + \includegraphics[scale=0.8]{byncsa30} +\end{center} +This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License. To +view a copy of this license, visit \url{http://creativecommons.org/licenses/by-nc-sa/3.0/} or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. \end{document}

1 0

[doc] batman-adv-doc, master: forgot to update makefile (caa417fc)
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 caa417fc81e7ed80028419a60661aa4771bf6f4f Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Fri Jan 2 11:58:13 2009 +0100 forgot to update makefile >--------------------------------------------------------------- caa417fc81e7ed80028419a60661aa4771bf6f4f images/Makefile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/images/Makefile b/images/Makefile index b36bed35..48c43730 100644 --- a/images/Makefile +++ b/images/Makefile @@ -1,6 +1,8 @@ GP_IMAGES=asym_penalty.gp DIA_IMAGES=asymetry.dia tq.dia eq.dia eq_alt1.dia eq_alt2.dia eq_alt3.dia rq.dia \ - hop_penalty1.dia hop_penalty2.dia asym_link1.dia asym_link2.dia tq_prop.dia + hop_penalty1.dia hop_penalty2.dia \ + hop_penalty3.dia hop_penalty4.dia hop_penalty5.dia hop_penalty6.dia \ + asym_link1.dia asym_link2.dia tq_prop.dia TEX_IMAGES=compute_tq.tex tq_prop_calc.tex PNG_IMAGES= $(DIA_IMAGES:.dia=.png) PNG_IMAGES+=$(GP_IMAGES:.gp=.png)

1 0

[doc] batman-adv-doc, master: rename source node (e13b8d1b)
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 e13b8d1b92132ed80b2aa1fe11c224d84054376a Author: Marek Lindner <lindner_marek(a)yahoo.de> Date: Fri Jan 2 12:15:22 2009 +0100 rename source node >--------------------------------------------------------------- e13b8d1b92132ed80b2aa1fe11c224d84054376a batman_iv.docbook | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/batman_iv.docbook b/batman_iv.docbook index cf05948c..2abbce83 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -284,7 +284,7 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, 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. This introduces a new problem: 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 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> <para> - Example topology: The node 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. + Example topology: 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. <inlinemediaobject> <imageobject> <imagedata fileref="images/hop_penalty3.pdf" format="EPS" scale="50" /> </imageobject> <imageobject> <imagedata fileref="images/hop_penalty3.png" format="PNG" /> </imageobject> @@ -303,7 +303,7 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, 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. 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. </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 SOURCE itself and node B (both will advertise the same TQ value). [bild3] + 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). [bild3] <inlinemediaobject> <imageobject> <imagedata fileref="images/hop_penalty5.pdf" format="EPS" scale="50" /> </imageobject> <imageobject> <imagedata fileref="images/hop_penalty5.png" format="PNG" /> </imageobject> @@ -311,7 +311,7 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, </inlinemediaobject> - As B.A.T.M.A.N. IV values TQ and fastest packet the node A's route will point towards the SOURCE node. Once the WiFi link quality drops (for a few moments due to some collisions) the TQ value from the SOURCE node 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. + 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> To overcome this issue B.A.T.M.A.N. IV introduces a hop penalty: Every time an OGM passes a node the TQ value will be decreased by a fixed value regardless of the asymetric link penalty before rebroadcasting the packet. In the given example it decrease the value of the second route via node B.

1 0

[doc] batman-adv-doc,master: minor fixes (38989eda)
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 38989eda48173d5437f9f14ae6238bfe33d43296 Author: Marek Lindner <lindner_marek(a)yahoo.de> Date: Fri Jan 2 12:37:04 2009 +0100 minor fixes >--------------------------------------------------------------- 38989eda48173d5437f9f14ae6238bfe33d43296 batman_iv.docbook | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/batman_iv.docbook b/batman_iv.docbook index 2abbce83..6e565986 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -300,10 +300,10 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, <textobject> <phrase>packet hops</phrase> </textobject> </inlinemediaobject> - 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. 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. + 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). [bild3] + 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). <inlinemediaobject> <imageobject> <imagedata fileref="images/hop_penalty5.pdf" format="EPS" scale="50" /> </imageobject> <imageobject> <imagedata fileref="images/hop_penalty5.png" format="PNG" /> </imageobject>

1 0

[doc] batman-adv-doc, master: change SOURCE to S in pictures (c010bb16)
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 c010bb166ae3c726d49d3d75ed14e8641e04443a Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Fri Jan 2 12:28:59 2009 +0100 change SOURCE to S in pictures >--------------------------------------------------------------- c010bb166ae3c726d49d3d75ed14e8641e04443a images/hop_penalty3.dia | Bin 1297 -> 1269 bytes images/hop_penalty4.dia | Bin 1448 -> 1414 bytes images/hop_penalty5.dia | Bin 1328 -> 1305 bytes images/hop_penalty6.dia | Bin 1453 -> 1419 bytes 4 files changed, 0 insertions(+), 0 deletions(-) diff --git a/images/hop_penalty3.dia b/images/hop_penalty3.dia index 26672e09..4ae03a75 100644 Binary files a/images/hop_penalty3.dia and b/images/hop_penalty3.dia differ diff --git a/images/hop_penalty4.dia b/images/hop_penalty4.dia index 5f093c01..ef16f62d 100644 Binary files a/images/hop_penalty4.dia and b/images/hop_penalty4.dia differ diff --git a/images/hop_penalty5.dia b/images/hop_penalty5.dia index 0e8d83a8..6cfe134e 100644 Binary files a/images/hop_penalty5.dia and b/images/hop_penalty5.dia differ diff --git a/images/hop_penalty6.dia b/images/hop_penalty6.dia index e002f695..281ca186 100644 Binary files a/images/hop_penalty6.dia and b/images/hop_penalty6.dia differ

1 0

[doc] batman-adv-doc, master: add target to compile batman_iv part only (84e61f83)
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 84e61f83107f4cb494f3d235cb4a4ed29063a0de Author: Simon Wunderlich <siwu(a)hrz.tu-chemnitz.de> Date: Sat Jan 3 15:35:16 2009 +0100 add target to compile batman_iv part only >--------------------------------------------------------------- 84e61f83107f4cb494f3d235cb4a4ed29063a0de Makefile | 4 ++++ batman.docbook => batman_iv_only.docbook | 4 ---- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index 09946e1e..b8cac436 100644 --- a/Makefile +++ b/Makefile @@ -4,6 +4,10 @@ all: batman_doc batman_doc: Makefile *.docbook images docbook2html batman.docbook docbook2pdf batman.docbook +batman_iv_only_doc: Makefile *.docbook images + docbook2html batman_iv_only.docbook + docbook2pdf batman_iv_only.docbook + images: make -C images/ clean: diff --git a/batman.docbook b/batman_iv_only.docbook similarity index 89% copy from batman.docbook copy to batman_iv_only.docbook index d3382aad..595da8c3 100644 --- a/batman.docbook +++ b/batman_iv_only.docbook @@ -9,11 +9,7 @@ <book id="batman_book" lang="en"> -&bookinfo; -&introduction; &batman_iv; -&batman_adv; -&usage; </book>

1 0

[doc] batman-adv-doc, master: TQ propagation update + echo cancellation (71ab9edf)
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 71ab9edfa08abed964578dd3472ea8fd96c1b305 Author: Marek Lindner <lindner_marek(a)yahoo.de> Date: Mon Jan 5 20:57:50 2009 +0100 TQ propagation update + echo cancellation >--------------------------------------------------------------- 71ab9edfa08abed964578dd3472ea8fd96c1b305 batman_iv.docbook | 139 +++++++++++++++++++++++++++++++++++------------------- 1 file changed, 90 insertions(+), 49 deletions(-) diff --git a/batman_iv.docbook b/batman_iv.docbook index 6e565986..1656017f 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -156,46 +156,57 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, </para> <para> As explained in the previous section the packet counting floods the network with receiving link quality rather than transmit link quality. On the link-local level the transmit link quality can be derived from the receiving link quality by applying some calculations on the packet count. - +</para> +<para> <orderedlist> <listitem> - <para>B.A.T.M.A.N. knows the receiving link quality (RQ) by counting the packets of its neighbors.</para> <para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/rq.pdf" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/rq.png" format="PNG" /> </imageobject> - <textobject> <phrase>Receive Quality (RQ)</phrase> </textobject> - </inlinemediaobject></para> + B.A.T.M.A.N. knows the receiving link quality (RQ) by counting the packets of its neighbors. + </para> + <para> + <inlinemediaobject> + <imageobject> <imagedata fileref="images/rq.pdf" format="EPS" scale="50" /> </imageobject> + <imageobject> <imagedata fileref="images/rq.png" format="PNG" /> </imageobject> + <textobject> <phrase>Receive Quality (RQ)</phrase> </textobject> + </inlinemediaobject> + </para> </listitem> <listitem> - <para>B.A.T.M.A.N. knows the echo link quality (EQ) by counting rebroadcasts of its own OGMs from his neighbors.</para> <para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/eq_alt1.pdf" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/eq_alt1.png" format="PNG" /> </imageobject> - <textobject> <phrase>Echo Link Quality (EQ)</phrase> </textobject> - </inlinemediaobject></para> + B.A.T.M.A.N. knows the echo link quality (EQ) by counting rebroadcasts of its own OGMs from his neighbors. + </para> + <para> + <inlinemediaobject> + <imageobject> <imagedata fileref="images/eq_alt1.pdf" format="EPS" scale="50" /> </imageobject> + <imageobject> <imagedata fileref="images/eq_alt1.png" format="PNG" /> </imageobject> + <textobject> <phrase>Echo Link Quality (EQ)</phrase> </textobject> + </inlinemediaobject> + </para> </listitem> <listitem> - <para>B.A.T.M.A.N. can calculate the transmit link quality (TQ) by dividing the echo link quality by the receiving link quality.</para> <para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/tq.pdf" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/tq.png" format="PNG" /> </imageobject> - <textobject> <phrase>Transmit Link Quality (TQ)</phrase> </textobject> - </inlinemediaobject></para> + B.A.T.M.A.N. can calculate the transmit link quality (TQ) by dividing the echo link quality by the receiving link quality. + </para> <para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/compute_tq.pdf" format="EPS"/> </imageobject> - <imageobject> <imagedata fileref="images/compute_tq.png" format="PNG" /> </imageobject> - <textobject> <phrase>compute the Transmit Link Quality</phrase> </textobject> - </inlinemediaobject> + <inlinemediaobject> + <imageobject> <imagedata fileref="images/tq.pdf" format="EPS" scale="50" /> </imageobject> + <imageobject> <imagedata fileref="images/tq.png" format="PNG" /> </imageobject> + <textobject> <phrase>Transmit Link Quality (TQ)</phrase> </textobject> + </inlinemediaobject> + </para> + <para> + <inlinemediaobject> + <imageobject> <imagedata fileref="images/compute_tq.pdf" format="EPS"/> </imageobject> + <imageobject> <imagedata fileref="images/compute_tq.png" format="PNG" /> </imageobject> + <textobject> <phrase>compute the Transmit Link Quality</phrase> </textobject> + </inlinemediaobject> </para> - </listitem> </orderedlist> - This shows that B.A.T.M.A.N. IV is able to compute the local Transmit Quality by using the same - mechanisms as B.A.T.M.A.N. III without adding further overhead. +</para> +<para> + This shows that B.A.T.M.A.N. IV is able to compute the local Transmit Quality by using the same + mechanisms as B.A.T.M.A.N. III without adding further overhead. </para> </sect2> <sect2 id="batman4_tq_prop"> @@ -222,8 +233,18 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, <imageobject> <imagedata fileref="images/tq_prop.png" format="PNG" /> </imageobject> <textobject> <phrase>TQ propagation</phrase> </textobject> </inlinemediaobject> - - +</para> +<para> + B.A.T.M.A.N. IV can not always rebroadcast the newly calculated TQ that came with the latest OGM. Instead the TQ that was received via the best neighbor is rebroadcasted to support asymetric link scenarios better. +</para> +<para> + Example: Node A and B are neighbors. Node A has a good connection towards node B but not vice versa. The node C has a good connection towards node A, has a good receiving link quality and bad sending quality towards B. [bild1] +</para> +<para> + Due to this layout the originator messages from node A have a good chance arriving at B but the TQ value propagated by node B is very low due to the high packet loss towards node A. The messages from node A that travel via node C have a low probablity arriving at node B due to the packet loss towards node B but have a much better TQ value. Node B will propagate many messages with a low TQ value (received from node A directly) and a few messages with a high TQ value (received from node A via node C) although the connection towards node A is very good. [bild2] +</para> +<para> + Therefore, B.A.T.M.A.N. IV will rebroadcast the received OGM with the TQ value of the best neighbor towards the originator. In the given example node B will place the TQ value received via node C in the message from node A before rebroadcasting it. It will flood its best TQ only. [bild3] </para> </sect2> @@ -250,31 +271,31 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, 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> <para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/asym_link1.pdf" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/asym_link1.png" format="PNG" scale="50" /> </imageobject> - <textobject> <phrase>Asymetry situation without asymetry penalty</phrase> </textobject> - </inlinemediaobject> + <inlinemediaobject> + <imageobject> <imagedata fileref="images/asym_link1.pdf" format="EPS" scale="50" /> </imageobject> + <imageobject> <imagedata fileref="images/asym_link1.png" format="PNG" scale="50" /> </imageobject> + <textobject> <phrase>Asymetry situation without asymetry penalty</phrase> </textobject> + </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. </para> <para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/asym_penalty.pdf" format="EPS" /> </imageobject> - <imageobject> <imagedata fileref="images/asym_penalty.png" format="PNG" /> </imageobject> - <textobject> <phrase>graph for asymetry penalty</phrase> </textobject> - </inlinemediaobject> + <inlinemediaobject> + <imageobject> <imagedata fileref="images/asym_penalty.pdf" format="EPS" /> </imageobject> + <imageobject> <imagedata fileref="images/asym_penalty.png" format="PNG" /> </imageobject> + <textobject> <phrase>graph for asymetry penalty</phrase> </textobject> + </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. </para> <para> - <inlinemediaobject> - <imageobject> <imagedata fileref="images/asym_link2.pdf" format="EPS" scale="50" /> </imageobject> - <imageobject> <imagedata fileref="images/asym_link2.png" format="PNG" /> </imageobject> - <textobject> <phrase>Asymetry situation with applied asymetry penalty</phrase> </textobject> - </inlinemediaobject> + <inlinemediaobject> + <imageobject> <imagedata fileref="images/asym_link2.pdf" format="EPS" scale="50" /> </imageobject> + <imageobject> <imagedata fileref="images/asym_link2.png" format="PNG" /> </imageobject> + <textobject> <phrase>Asymetry situation with applied asymetry penalty</phrase> </textobject> + </inlinemediaobject> </para> </sect2> @@ -285,36 +306,44 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, </para> <para> Example topology: 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.pdf" 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.pdf" 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.pdf" 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> To overcome this issue B.A.T.M.A.N. IV introduces a hop penalty: Every time an OGM passes a node the TQ value will be decreased by a fixed value regardless of the asymetric link penalty before rebroadcasting the packet. In the given example it decrease the value of the second route via node B. +</para> +<para> <inlinemediaobject> <imageobject> <imagedata fileref="images/hop_penalty6.pdf" format="EPS" scale="50" /> </imageobject> <imageobject> <imagedata fileref="images/hop_penalty6.png" format="PNG" /> </imageobject> @@ -327,7 +356,19 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, <sect2 id="batman4_tq_echo_cancellation"> <title>Echo cancellation</title> <para> - TODO rebroadcast cancellation by adding IP of previous node because we don't drop packets + As explained in the hop penalty section B.A.T.M.A.N. IV floods the network with more packets than B.A.T.M.A.N. III due to the less strict duplicate detection mechanism. B.A.T.M.A.N. IV checks for unknown sequence numbers via a specific neighbor. 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> +<para> + Lets consider the following example: 3 nodes (A, B and C) in a row (A can hear B but not C). Node A emits an OGM, B hears and rebroadcasts it. This broadcast from B arrives at C which also rebroadcasts the message. B will receive the very OGM that it sent before and happily rebroadcast again (the echo of its own message). [figure1] +</para> +<para> + To detect echos (messages that already passed through a node) B.A.T.M.A.N. IV introduces a new protocol field called "old originator" which contains the IP address of the node rebroadcasting the OGM. Whenever a node receives a message from a neighbor it will fill the "old originator" field with the address of this neighbor before rebroadcasting it. If the neighbor recognizes his own IP address in the "old originator" field the packet will be ignored. [figure2] +</para> +<para> + Back to the example: Node B will ignore (drop) the packet coming back from node C as node C wrote the IP address of node B in the "old originator" field. [figure3] +</para> +<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. [figure4] </para> </sect2>

1 0

← Newer
1
...
12
13
14
15
16
17
18
...
25
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits December 2017