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

metadata review

This commit is contained in:
emmajane 2004-04-19 21:33:22 +00:00
parent 1d0d30f9e1
commit fb7b5cb60c
1 changed files with 82 additions and 61 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -18,8 +18,19 @@
<!-- Valid email -->
<address><email>lars (at) unik no</email></address>
</affiliation>
<authorinitials>LKS</authorinitials>
</author>
<authorinitials>LKS</authorinitials>
<editor>
<firstname>Emma Jane</firstname>
<surname>Hogbin</surname>
<contrib>Metadata and markup review of 0.6.</contrib>
</editor>
<editor>
<firstname>Thomas</firstname>
<surname>Zimmerman</surname>
<contrib>Language review of 0.5.</contrib>
</editor>
<!-- All dates specified in ISO "YYYY-MM-DD" format -->
<pubdate>2004-04-19</pubdate>
@ -336,15 +347,15 @@ Working Group</ulink>.
<listitem>
<para>The <userinput>olsrd</userinput> gets installed to
<userinput>/usr/bin/</userinput> and a default config file,
<userinput>olsrd.conf</userinput> can be found under
<userinput>/etc</userinput></para>
<filename class='directory'>/usr/bin/</filename> and a default config file,
<filename>olsrd.conf</filename> can be found under
<filename class="directory">/etc</filename></para>
</listitem>
</orderedlist>
</para>
<para>Check out the <userinput>/etc/olsrd.conf</userinput> config
<para>Check out the <filename>/etc/olsrd.conf</filename> config
file, and change values to fit your system. All values in this file
can be overridden with command line options to
<userinput>olsrd</userinput>. The main options to change are:</para>
@ -388,7 +399,7 @@ Working Group</ulink>.
<prompt># </prompt><userinput><command>olsrd</command></userinput>
</programlisting>
<para>All the settings in <userinput>/etc/olsrd.conf</userinput>
<para>All the settings in <filename>/etc/olsrd.conf</filename>
can be overridden by command line options:</para>
<programlisting>
@ -440,7 +451,7 @@ Working Group</ulink>.
<callout arearefs="tuning">
<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
(<filename>/etc/olsrd.conf</filename>) or specify it 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>
@ -542,7 +553,7 @@ Working Group</ulink>.
<callout arearefs="triangle">
<para>
After a short time, when all nodes has been updated and routes
After a short time, when all nodes have been updated and routes
calculated, we may also reach any of the other nodes via the
other. The 2-hop neighbor list
(<userinput>[2hlist:]</userinput>) is populated: We can reach node
@ -584,9 +595,9 @@ Working Group</ulink>.
<title>Movement</title>
<para>
When every node can reach every other node, it's no fun. Lets
When every node can reach every other node, it's no fun. Let's
start moving the nodes, so that node <quote>A</quote> and
<quote>B</quote> is out of (radio) range of each other. So when
<quote>B</quote> are out of (radio) range of each other. So when
we move node <quote>A</quote> far enough away so that
it can't hear node <quote>C</quote>, all traffic must go through
node <quote>B</quote>: </para>
@ -608,10 +619,8 @@ Working Group</ulink>.
</caption>
</mediaobject>
<para></para>
<para>
Tip: Instead of physically moving the nodes around, you can use
Tip: Instead of physically moving the nodes around, you can use
<userinput>ip6tables</userinput>. You can drop all packet using the
MAC-address. You just need to block on one node:
</para>
@ -702,7 +711,7 @@ Working Group</ulink>.
<para>
To have one node, act as a gateway and send out HNA messages, you
must change the <userinput>HNA6</userinput> in
<userinput>/etc/olsrd.conf</userinput>:
<filename>/etc/olsrd.conf</filename>:
</para>
<screen>
@ -748,7 +757,8 @@ Working Group</ulink>.
<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"
forwarded by all the nodes by the <quote>default forwarding
algorithm</quote>
(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>
@ -765,7 +775,8 @@ Working Group</ulink>.
<para>
OLSRd also has an optional GUI, which can show a list of
available nodes and grab packets. To compile the GUI front end,
you must have GTK2. In <userinput>unik-olsrd-x.y.z</userinput>
you must have GTK2. In <filename
class="directory">unik-olsrd-x.y.z</filename>
directory do:
</para>
@ -776,13 +787,13 @@ Working Group</ulink>.
<prompt>#</prompt> <userinput><command>make</command> install</userinput>
</screen>
<para>
<emphasis>Note! Remember to start OLSRd with the
<note><para>
Remember to start OLSRd with the
<userinput>-ipc</userinput> switch or set
<userinput>IPC-CONNECT yes</userinput> in
<userinput>/etc/olsrd.conf</userinput> to enable the GUI to chat
with OLSRd.</emphasis>
</para>
with OLSRd.
</para></note>
<para>
To see some examples of the use of GUI, check out <ulink
@ -806,8 +817,8 @@ Working Group</ulink>.
<para>INRIA was one of the first(?) implementation of OLSR <ulink
url="http://hipercom.inria.fr/olsr/#code">http://hipercom.inria.fr/olsr/#code</ulink>.
Their web-site has not been updated for quite a while, and the
OLSR code you can download only comply to
draft-ietf-manet-olsr-03.txt (it's now a RFC). There is suppose to
OLSR code you can download only complies to
draft-ietf-manet-olsr-03.txt (it's now an RFC). There is suppose to
be another more up-to-date version of INRIA olsr, but I have not
found it. INRIA OLSR does not support IPv6.</para>
@ -830,7 +841,7 @@ Working Group</ulink>.
<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) in Canada. But as of this writing,
it has been no new releases since April 3, 2003. <ulink
there have 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>
</sect3>
@ -857,60 +868,71 @@ Working Group</ulink>.
<para>Some of these question/answers are from the <ulink
url="http://www.olsr.org">OLSRd</ulink> site.</para>
<orderedlist>
<listitem>
<para><emphasis>Q: If OLSRd fully RFC3626
compliant?</emphasis></para>
<para>A: Yes. It even has implemented some of the extra
<qandaset>
<qandaentry>
<question>
<para>If OLSRd fully RFC3626 compliant?</para>
</question>
<answer>
<para>Yes. It even has implemented some of the extra
functionality mentioned in the RFC. See the <ulink
url="http://www.olsr.org/index.cgi?action=comp">
RFC Compliance</ulink> section for complete list.
</para>
</listitem>
</answer>
</qandaentry>
<listitem>
<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
designed to be used concurrently. The network topology can be
<qandaentry>
<question>
<para>Can I mix site-local and global IPv6 addresses?</para>
</question>
<answer>
<para>Yes. But keep in mind that they intentionally were not
designed to be used at the same time. The network topology can be
quite <quote>messy</quote> if you start using these two.
</para>
</listitem>
</answer>
</qandaentry>
<listitem>
<para><emphasis>Q: The GUI front-end failed to
compile...why?</emphasis></para>
<para>A: You probably don't have GTK2.0 development libraries
<qandaentry>
<question>
<para>The GUI front-end failed to compile...why?</para>
</question>
<answer>
<para>You probably don't have the GTK2.0 development libraries
installed.</para>
</listitem>
</answer>
</qandaentry>
<listitem>
<para><emphasis>Q: If there is multiply gateways present, how does
the mobile node conclude to use the nearest one?</emphasis></para>
<para>A: When a new gateway is detected, the Mobile Node check the
<qandaentry>
<question>
<para>If there is multiply gateways present, how does
the mobile node conclude to use the nearest one?</para>
</question>
<answer>
<para>When a new gateway is detected, the Mobile Node checks the
distance (number of hops) to this newly discovered gateway
compared to the current gateway. If there is a shorter distance,
this new gateway becomes the current (default) gateway. See
section 12.6.2 in the OLSR RFC (<ulink
url="http://www.ietf.org/rfc/rfc3626.txt">RFC3626</ulink>)</para>
</listitem>
</answer>
</qandaentry>
<listitem>
<para><emphasis>Q: I get OLSRd up and running - but the nodes
don't seem to <quote>hear</quote> each other!</emphasis></para>
<para>A: Most of the time this is a configuration error: Check
<qandaentry>
<question>
<para>I get OLSRd up and running - but the nodes
don't seem to <quote>hear</quote> each other!</para>
</question>
<answer>
<para>Most of the time this is a configuration error: Check
the following:
<itemizedlist>
<listitem>
If using WLAN interfaces make sure the ESSID/key match.
</listitem>.
</listitem>
<listitem>
Make sure the cards are set in <quote>ad-hoc</quote> mode
@ -923,13 +945,12 @@ Working Group</ulink>.
to see what rules are set. <userinput>ip6tables
-F</userinput> flushes all rules.
</listitem>
</itemizedlist>
</para>
</answer>
</qandaentry>
</qandaset>
</para>
</listitem>
</orderedlist>
</sect1>