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

On branches: batman-adv-doc,master

commit cf94e907a4a30b6c3a6d91209c2bc4c126c538a5 Author: Simon Wunderlich siwu@hrz.tu-chemnitz.de Date: Mon Aug 25 16:57:27 2008 +0200

add first illustration and infrastructure for png/eps

Illustrations are done in dia (vector editing program) and then converted to png (for html) and eps (for pdf). The eps output looks bad on my system, that's hopefully just a bug over here... :(

cf94e907a4a30b6c3a6d91209c2bc4c126c538a5 Makefile | 6 +++++- batman_iv.docbook | 7 ++++++- images/Makefile | 17 +++++++++++++++++ images/asymetry.dia | Bin 0 -> 1396 bytes 4 files changed, 28 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile index 3f2f1c9f..b25f1e3d 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,11 @@ default: all all: batman_doc -batman_doc: Makefile *.docbook +.PHONY: clean images +batman_doc: Makefile *.docbook images docbook2html batman.docbook docbook2pdf batman.docbook +images: + make -C images/ clean: rm -rf *.html *.pdf + make -C images clean diff --git a/batman_iv.docbook b/batman_iv.docbook index 0540c2ac..e9e0472c 100644 --- a/batman_iv.docbook +++ b/batman_iv.docbook @@ -87,7 +87,12 @@ TODO Explain multiple interfaces, which interface sends which OGM by which TTL, The B.A.T.M.A.N. III algorithm has serious problems when it comes to asymetric links. The bidirectional link check tries to limit its impact but the result is far from being perfect. The timeframe in which B.A.T.M.A.N. accepts his own OGMs being rebroadcasted by its neighbor allows to tweak the behaviour. If this timeframe is rather short B.A.T.M.A.N. is very strict on choosing links. This may lead to many ignored links which might be usable in one direction. Only symetric connections will be considered. If the timeframe value is less strict B.A.T.M.A.N. will accept more links but tends to route in the wrong direction. </para> <para> - Example: OGMs from Node A propagate to B. The link is asymetric, therefore B receives all packets from A in contrast to A which receives almost nothing from B. As all the packets from A get to B the packet count at B's side goes up. B will assume that it has a perfect link towards A which is not the case. [illustration needed] + Example: OGMs from Node A propagate to B. The link is asymetric, therefore B receives all packets from A in contrast to A which receives almost nothing from B. As all the packets from A get to B the packet count at B's side goes up. B will assume that it has a perfect link towards A which is not the case. +<inlinemediaobject> + <imageobject> <imagedata fileref="images/asymetry" format="EPS" /> </imageobject> + <imageobject> <imagedata fileref="images/asymetry.png" format="PNG" /> </imageobject> + <textobject> <phrase>asymetry illustration</phrase> </textobject> +</inlinemediaobject> </para> <para> To overcome this flaw B.A.T.M.A.N. IV has been enhanced with the Transmit Quality (TQ) algorithm. The following section is going to outline its design and how it strengthens B.A.T.M.A.N.'s routing capabilities in asymetric environments. diff --git a/images/Makefile b/images/Makefile new file mode 100644 index 00000000..627d1354 --- /dev/null +++ b/images/Makefile @@ -0,0 +1,17 @@ +DIA_IMAGES=asymetry.dia +PNG_IMAGES=$(DIA_IMAGES:.dia=.png) +EPS_IMAGES=$(DIA_IMAGES:.dia=.eps) + +.PHONY: clean +.SUFFIXES: .dia .png .eps + +default: all +all: $(EPS_IMAGES) $(PNG_IMAGES) + +.dia.png: + /usr/bin/dia -e $@ $< +.dia.eps: + /usr/bin/dia -e $@ $< + +clean: + rm *.png *.eps diff --git a/images/asymetry.dia b/images/asymetry.dia new file mode 100644 index 00000000..9cc362bc Binary files /dev/null and b/images/asymetry.dia differ