[Olsr-cvs] olsrd-current README,1.15,1.16

Andreas T�nnesen (spam-protected)
Wed Nov 23 06:51:10 CET 2005


Update of /cvsroot/olsrd/olsrd-current
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23602

Modified Files:
	README 
Log Message:
Some initial 0.4.10 changes to the README file

Index: README
===================================================================
RCS file: /cvsroot/olsrd/olsrd-current/README,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** README	2 Jun 2005 15:49:11 -0000	1.15
--- README	23 Nov 2005 05:51:07 -0000	1.16
***************
*** 1,5 ****
  
  +====================================================================+
! | README - olsr.org OLSR daemon 0.4.8, 05.12.04                      |
  +====================================================================+
  
--- 1,5 ----
  
  +====================================================================+
! | README - olsr.org OLSR daemon 0.4.10, 23.11.05                     |
  +====================================================================+
  
***************
*** 44,58 ****
  routing protocol. The protocol is documented in RFC3626. The website
  of olsrd is http://www.olsr.org
- Olsrd started out as part of the master thesis project for Andreas Tønnesen 
- at UniK University Graduate Center in Norway. This master thesis is now 
- finished(it is available for download at the olsrd website) but the olsrd 
- project moves on. Initially olsrd only compiled for GNU/Linux systems.
- Then Thomas Lopatic joined up with the project in aug. 04 and he has seen 
- to it that olsrd now, also compiles on MS-Windows, Mac OSX and FreeBSD.
  
  Olsrd is designed to be a modular an extensible implementation. It features
  a plugin interface, allowing for developers to extend OLSR operation without
  interfering with the core code. It also features a experimental link quality
! routing scheme, by Thomas and people at the c-base in Berlin.
  
  To ask questions or make comments, join up with the mailing lists:
--- 44,52 ----
  routing protocol. The protocol is documented in RFC3626. The website
  of olsrd is http://www.olsr.org
  
  Olsrd is designed to be a modular an extensible implementation. It features
  a plugin interface, allowing for developers to extend OLSR operation without
  interfering with the core code. It also features a experimental link quality
! routing scheme.
  
  To ask questions or make comments, join up with the mailing lists:
***************
*** 64,68 ****
  
  Olsrd source or binaries can be downloaded from olsr.org. CVS is available
! for the brave ;)
  
  
--- 58,62 ----
  
  Olsrd source or binaries can be downloaded from olsr.org. CVS is available
! for the cutting edge features ;-)
  
  
***************
*** 80,84 ****
  compliant in that it will inter-operate with other RFC3626 implementations.
  Internally there are a few things that are solved differently that proposed 
! in the RFC. Check out the "Conclusions" section of my master thesis for details.
  
  
--- 74,80 ----
  compliant in that it will inter-operate with other RFC3626 implementations.
  Internally there are a few things that are solved differently that proposed 
! in the RFC. Check out the "Conclusions" section of the "Implementing And
! Extending The Optimized Link State routing Protocol" thesis available at
! olsr.org.
  
  
***************
*** 96,102 ****
   * Users are free to implement olsrd plugins and license them under whatever 
     terms they like.
!  * If you, unlike yours truly, don't love C, the plugins can be written in 
!    any language that can be compiled as a dynamic library. Linux even allows 
!    scripts!
   * No need for people with extended OLSR versions to rely on heavy patching 
     to maintain functionality when new olsrd versions are released.
--- 92,97 ----
   * Users are free to implement olsrd plugins and license them under whatever 
     terms they like.
!  * The plugins can be written in any language that can be compiled as 
!    a dynamic library. Linux even allows scripts!
   * No need for people with extended OLSR versions to rely on heavy patching 
     to maintain functionality when new olsrd versions are released.
***************
*** 119,122 ****
--- 114,126 ----
    Plugins that are part of this release(can be found in the lib/ directory):
  
+   - Tiny Application Server(TAS).
+ 
+   - HttpInfo. This plugin implements a simple HTTP server that serves dynamic
+     pages with lots of information about the running olsrd process.
+ 
+   - Mini.
+ 
+   - Nameservice.
+ 
    - Dynamic Internet gateway. A plugin that dynamically adds and removes Internet
      HNA transmissions based on if there exists a default gateway to Internet
***************
*** 133,138 ****
  
    - Power plugin. A plugin that uses OLSRs MPR flooding to spread information
!     about the power status of nodes. Meant as an example plugin to get coders
!     started.
  
  
--- 137,142 ----
  
    - Power plugin. A plugin that uses OLSRs MPR flooding to spread information
!     about the power status of nodes. Meant as an example plugin for code
!     reference only.
  
  
***************
*** 150,167 ****
  ==================
  
- We suspect that in the previous version 0.4.7 OLSR traffic, in
- particular HELLO messages, is more prone to packet loss than data
- traffic. We think so, because the OLSR people of Vienna have excellent
- links but link detection reports links as broken very often. This
- problem exists in 0.4.7. We think that the reason for this is that in
- multi-interface configurations olsrd 0.4.7 sends HELLO messages via
- all interfaces at the same time without any jitter, which probably
- results in interference, as HELLO messages from different interfaces
- "collide". 0.4.8 should solve this problem, as we now have
- per-interface jitter when sending HELLO messages. So collisions
- between HELLO messages of different interfaces should be significantly
- reduced. So, if you have a multi-interface configuration, too, please
- let us know if you observe anything unusual. We'll also keep
- investigating this problem with the Vienna guys.
  
  ===============
--- 154,157 ----
***************
*** 169,180 ****
  ===============
  
! As the 0.4.8 release contains huge amounts of new code, the releases up to 0.5 
! will focus much on bug fixing. If relatively serious bugs are found new releases
! will be made fixing thees issues.
! Asides from that there will be some focus on redesigning the IPC interface, and
! hopefully we will end up with a neat platform independent GUI front-end to
! work over this new IPC interface.
! IPv6 support for Windows, FreeBSD and OSX will also be an issue.
! 
  
  ----------------------------------------------------------------------
--- 159,165 ----
  ===============
  
! Future releases of the 0.4 series will be maintainance releases focused
! on bugfixing. Work will soon begin on a 0.5 series where we will focus
! much more on new ideas. 0.4 and 0.5 might coexist for some time. 
  
  ----------------------------------------------------------------------
***************
*** 186,192 ****
  =======================
  
! Olsrd is implemented in pure C with very few dependencies. The 0.4.8
! release has removed the pthread dependency making olsrd even more
! portable! Olsrd is known to run on various hardware like:
   * x86    - your regular PC
   * PPC    - Macintosh hardware
--- 171,176 ----
  =======================
  
! Olsrd is implemented in pure C with very few dependencies. Olsrd is 
! known to run on various hardware like:
   * x86    - your regular PC
   * PPC    - Macintosh hardware
***************
*** 216,220 ****
  ------------------------------------------------------------
  olsrd		+/+	+/+	+/+	+/+	+/+	?
! olsr_switch	+/+	+/?	+/+	+/+	+/+	?
  ------------------------------------------------------------
  PLUGINS
--- 200,204 ----
  ------------------------------------------------------------
  olsrd		+/+	+/+	+/+	+/+	+/+	?
! olsr_switch	+/+	+/+	+/+	+/+	+/+	?
  ------------------------------------------------------------
  PLUGINS
***************
*** 238,244 ****
  =================
  
! A GUI front end for GNU/Linux using GTK is available in the gui/ directory.
! this implementation is really no longer supported, but it should work with
! 0.4.8 except that it will not show correct configuration parameters.
  
  There currently is, however, a native MFC-based Windows GUI. Unlike
--- 222,228 ----
  =================
  
! A GUI front end for GNU/Linux using GTK is available in the gui/ 
! directory. This implementation is no longer supported, and might
! not work any more. It will be completly removed in a future release.
  
  There currently is, however, a native MFC-based Windows GUI. Unlike
***************
*** 333,353 ****
  =========
  
! To build olsrd you need to have all the regular development tools installed.
! This includes gcc, make, glibc, makedep etc.
! To install to a directory different from /(/etc, /usr/bin) use INSTALL_PREFIX=targetdir
! To use other compilers set CC=yourcompiler
  
  To build:
!  make OS=linux
  To install(as root):
   make install
  To delete object files run:
   make clean
  
! 
! Before running olsrd you must edit the default configuration file /etc/olsrd.conf
! adding at least what interfaces olsrd is to run on. Options in the config file can 
! also be overridden by command line options. See the manual pages olsrd(8) and 
! olsrd.conf(5) for details.
  The binary is named 'olsrd' and is installed in (PREFIX)/usr/sbin. 
  You must have root privileges to run olsrd!
--- 317,338 ----
  =========
  
! To build olsrd you need to have all the regular development tools 
! installed. This includes gcc, make, glibc, makedep etc.
! To install to a directory different from /(/etc, /usr/bin) use 
! INSTALL_PREFIX=targetdir. To use other compilers set CC=yourcompiler.
  
  To build:
!  make
  To install(as root):
   make install
  To delete object files run:
   make clean
+ Optionally, to clean all generated files:
+  make uberclean
  
! Before running olsrd you must edit the default configuration file 
! /etc/olsrd.conf adding at least what interfaces olsrd is to run on. 
! Options in the config file can also be overridden by command line 
! options. See the manual pages olsrd(8) and olsrd.conf(5) for details.
  The binary is named 'olsrd' and is installed in (PREFIX)/usr/sbin. 
  You must have root privileges to run olsrd!
***************
*** 355,360 ****
  olsrd
  
! If debug level is set to 0 olsrd will detach and run in the background, if not
! it will keep running in your shell.
  
  ===========
--- 340,345 ----
  olsrd
  
! If debug level is set to 0 olsrd will detach and run in the background, 
! if not it will keep running in your shell.
  
  ===========
***************
*** 368,372 ****
  and Mingw32. Simply use
  
!   make OS=win32
  
  to build the olsrd executable. Building the dot_draw plugin works
--- 353,357 ----
  and Mingw32. Simply use
  
!   make
  
  to build the olsrd executable. Building the dot_draw plugin works
***************
*** 426,440 ****
  
  
! ===========
!  * FREEBSD
! ===========
  
! The FreeBSD version is an initial port. It has not been extensively
! tested beyond "doesn't core dump and it looks like it adds routes". In
! order to build it, you need GNU make. Then use
  
!   gmake OS=fbsd
  
! to build the olsrd executable. Then say
  
    gmake install
--- 411,427 ----
  
  
! =========================
!  * FREEBSD/NETBSD/OPENBSD
! =========================
  
! The FreeBSD port should be relativley stable at this point.
! The OpenBSD and NetBSD versions are pretty much untested. They have 
! not been extensively tested beyond "doesn't core dump and it looks 
! like it adds routes". In order to build it, you need GNU make. Then 
! use:
  
!   gmake
  
! to build the olsrd executable. Then do:
  
    gmake install
***************
*** 450,457 ****
  The OS X port is a direct descendant of the FreeBSD port. So, the same
  limitations with respect to testing and maturity apply. Building and
! installing works in the same was as on FreeBSD, except that you have
! to use "osx" instead of "fbsd", as in
! 
!   gmake OS=osx
  
  
--- 437,441 ----
  The OS X port is a direct descendant of the FreeBSD port. So, the same
  limitations with respect to testing and maturity apply. Building and
! installing works in the same was as on FreeBSD.
  
  





More information about the Olsr-cvs mailing list