LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Updates post language review from Thomas Zimmerman.

This commit is contained in:
emmajane 2004-04-19 20:03:56 +00:00
parent e140408603
commit 1d0d30f9e1
1 changed files with 51 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
LDP/howto/docbook/OLSR-IPv6-HOWTO/OLSR-IPv6-HOWTO.xml
View File

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" []>
<article>
<articleinfo>
@ -22,10 +22,18 @@
<authorinitials>LKS</authorinitials>
<!-- All dates specified in ISO "YYYY-MM-DD" format -->
<pubdate>2004-03-08</pubdate>
<pubdate>2004-04-19</pubdate>
<!-- Most recent revision goes at the top; list in descending order -->
<revhistory>
<revision>
<revnumber>0.6</revnumber>
<date>2004-04-19</date>
<authorinitials>LKS</authorinitials>
<revremark>Thanks to Thomas Zimmerman &lt;thomas (at) zimres
net> for a language review! Updated to latest version number and
a section on plugin-support in OLSRd.</revremark>
</revision>
<revision>
<revnumber>0.5</revnumber>
<date>2004-03-08</date>
@ -84,7 +92,7 @@
particular purpose (improvised, made up in an instant)</quote>
(source: <ulink
url="http://en.wikipedia.org/wiki/List_of_Latin_phrases#A">Wikipedia</ulink>).
Ad-hoc network, or <quote>spontaneous network</quote>, is
An Ad-hoc network, or <quote>spontaneous network</quote>, is
especially useful when dealing with wireless devices in which some
of the devices are part of the network only for the duration of a
communications session and the need for a dynamic network topology
@ -146,7 +154,7 @@
developed for mobile ad hoc networks. It operates as a table
driven, proactive protocol, i.e., exchanges topology information
with other nodes of the network regularly. Each node selects a
set of its neighbor nodes as <quote>multipoint relays</quote>
set of its neighbor nodes as <quote>multi-point relays</quote>
(MPR). In OLSR, only nodes, selected as such MPRs, are
responsible for forwarding control traffic, intended for diffusion
into the entire network. MPRs provide an efficient mechanism for
@ -202,11 +210,10 @@
<para>
So why use OLSR when we can use <quote>IEEE ad-hoc
mode</quote>? <emphasis>IEEE ad-hoc mode does NOT support
multihop.</emphasis> See <link linkend="multihop">figure
multi-hop.</emphasis> See <link linkend="multihop">figure
below</link>
</para>
<mediaobject id="multihop">
<imageobject>
<imagedata fileref="images/multihop.png" format="PNG"
@ -218,7 +225,7 @@
<caption>
<para><quote>IEEE 8102.11 Ad hoc</quote> mode has
<emphasis>no</emphasis> support for multihop, something OLSR
have.</para>
does have.</para>
</caption>
</mediaobject>
@ -284,7 +291,7 @@ Working Group</ulink>.
<para>
OLSRd is an implementation based on the INRA C code, but has been
almost completely rewritten, so there is not much left of the original
INRA code (that mean it almost GPL). OLSRd also has a very rapid
INRA code (that mean it almost GPL). OLSRd also is under very rapid
development, and if you report in a bug, it is usually fixed in a
matter of hours.
</para>
@ -292,10 +299,11 @@ Working Group</ulink>.
<para>
OLSRd <ulink
url="http://www.olsr.org/index.cgi?action=comp">fully comply</ulink>
to the OLSR RFC, and it has an optional GUI interface (to see what's
going on). The implementation also has a informative
<quote>up-to-date</quote> <ulink
url="http://www.olsr.org">web-page</ulink> with mailing lists and papers.
to the OLSR RFC, support for plugins, and it has an optional GUI
interface (to see what's going on). The implementation also has a
informative <quote>up-to-date</quote> <ulink
url="http://www.olsr.org">web-page</ulink> with links to mailing
lists and papers.
</para>
<!-- ################## -->
@ -309,7 +317,7 @@ Working Group</ulink>.
<orderedlist>
<listitem>
<para> The latest release as of this writing is 0.4.0, but by the
<para> The latest release as of this writing is 0.4.3, but by the
time you read this there is almost certain a new release. Fetch the
latest release from <ulink
url="http://www.olsr.org/index.cgi?action=download">
@ -396,7 +404,7 @@ Working Group</ulink>.
<screen>
<prompt># </prompt><userinput><command>olsrd</command> -i eth1 -d 1 -ipv6</userinput>
*** UniK olsrd-0.4.0 ***
*** UniK olsrd-0.4.3 ***
hello interval = 2.00 hello int nonwireless: = 4.00 <co id="tuning"/>
tc interval = 5.00 polling interval = 0.10
@ -430,9 +438,9 @@ Working Group</ulink>.
<calloutlist>
<callout arearefs="tuning">
<para>This shows all the settings OLSRd are using. You may
override these by either specify it in the config file
(<userinput>/etc/olsrd.conf</userinput>) or specify it at the
<para>This shows all the settings OLSRd is using. You may
override these by either specifying it in the config file
(<userinput>/etc/olsrd.conf</userinput>) or specifly at the
command line. Read the <ulink
url="http://www.ietf.org/rfc/rfc3626.txt">OLSR RFC</ulink> for a
description on what all these settings means.</para>
@ -446,8 +454,8 @@ Working Group</ulink>.
<callout arearefs="adr">
<para>If you are using OLSRd with multiple interfaces, it will
pick one as the <quote>main</quote> address (the first
interface specified).</para>
pick the first interface specified as the <quote>main</quote>
address.</para>
</callout>
<callout arearefs="list">
@ -512,7 +520,8 @@ Working Group</ulink>.
<userinput>fec0:106:2700::11</userinput> is willing to forward
traffic. A host with low battery may not be willing to forward
large amount of traffic, - so it will proclaim a lower
willingness value.
willingness value (routing based on powerstatus is available as a
plugin).
</para>
</callout>
@ -733,6 +742,22 @@ Working Group</ulink>.
</para>
</sect2>
<!-- ################## -->
<sect2 id="plugins">
<title>Plugin support</title>
<para>As of version 0.4.3 OLSRd also support plugins. Plugins may be
used to add extended functionality in a MANET. If only a subset of
the nodes knows how to interpret the messagetype, it will be
forwarded by all the nodes by the "default forwarding algorithm"
(see section 3.4.1 in the <ulink
url="http://ietf.org/rfc/rfc3626.txt">OLSR RFC</ulink>). This way
certain nodes may add special functionlity into OLSR.</para>
<para>As of this writing, two example plugins is included in the
OLSRd release. One of these plugins add routing based on
powerstatus. If one node has low battery, it can set its willingness
lower and traffic may be routed through other nodes.</para>
</sect2>
<!-- ################## -->
<sect2 id="gui">
@ -770,8 +795,8 @@ Working Group</ulink>.
<!-- ################## -->
<sect2 id="other">
<title>Other OLSR implementations</title>
<para>There is also other OLSR implementations, none have gain so
much popularity as OLSRd, and none of them (expect <ulink
<para>There is also other OLSR implementations, none have gained as
much popularity as OLSRd, and none of them (except <ulink
url="http://qolsr.lri.fr/">QOLSR</ulink>?) are fully RFC
compliant.</para>
@ -784,7 +809,7 @@ Working Group</ulink>.
OLSR code you can download only comply to
draft-ietf-manet-olsr-03.txt (it's now a RFC). There is suppose to
be another more up-to-date version of INRIA olsr, but I have not
found it. INRIA OLSR has not support for IPv6.</para>
found it. INRIA OLSR does not support IPv6.</para>
</sect3>
@ -804,7 +829,7 @@ Working Group</ulink>.
<title>CRCOLSR</title>
<para>CRCOLSR is a implementation based on the French INRIA
code. It is is supposed to be maintained by <quote>Communication
Research Center</quote> (CRC) i Canada. But as of this writing,
Research Center</quote> (CRC) in Canada. But as of this writing,
it has been no new releases since April 3, 2003. <ulink
url="http://pf.itd.nrl.navy.mil/projects/olsr/">
http://pf.itd.nrl.navy.mil/projects/olsr/</ulink></para>
@ -845,7 +870,7 @@ Working Group</ulink>.
</listitem>
<listitem>
<para><emphasis>Q: Can i mix site-local and global IPv6
<para><emphasis>Q: Can I mix site-local and global IPv6
addresses?</emphasis></para>
<para>A: Yes. But keep in mind that they intentionally was not
@ -856,7 +881,7 @@ Working Group</ulink>.
<listitem>
<para><emphasis>Q: The GUI front-end failed to
compile... why?</emphasis></para>
compile...why?</emphasis></para>
<para>A: You probably don't have GTK2.0 development libraries
installed.</para>