[Olsr-users] OLSR Basic Block Diagram

Bhat, Ishwara (spam-protected)
Tue Nov 18 13:31:59 CET 2008



I have very basic questions on OLSR. This is what I understood from RFC,
OLSR_Report document and also from code study. Please tell me if I'm
right or wrong:


1.	OLSRd continuously watches the network and keeps updating
kernel's routing tables. (In the next version of OLSR there would be
optional specified RT table. But this is only for debugging)


2.	Let us say we have  a data packet originating at an external
machine and is destined to an IP address which is part of OLSR mesh.
Such a packet / originator need not be concerned about the existence of
OLSR at all.


        If I care only about routing packets to static IP addresses,
then I do not need to do anything at all. (I do not even need to get
basic management information. So no need for even txtinfo plugin).  Is
this correct ?


    Attached MS word document has a block diagram. Please confirm if
this is correct. I know it is too basic. But still wanted to verify. 



Thanks a lot !



"This e-mail, and any attachments thereto, are intended only for use by
the addressee(s) named herein and may contain privileged and/or
confidential information. If you are not the intended recipient of this
e-mail, you are hereby notified that any dissemination, distribution or
copying of this e-mail, and any attachments thereto, is illegal and
strictly prohibited. If you have received this e-mail in error, please
immediately notify me by telephone and permanently delete the original
and any copy of any e-mail and any printout thereof."


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20081118/9c9d6534/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OLSRDArchitecture.doc
Type: application/msword
Size: 42496 bytes
Desc: OLSRDArchitecture.doc
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20081118/9c9d6534/attachment.doc>

More information about the Olsr-users mailing list