The following commit has been merged in the master branch: commit fdf053af6208ece48362f9f684f65dfda4b1db4d Author: Corinna 'Elektra' Aichele onelektra@gmx.net Date: Fri Dec 8 16:37:56 2006 +0100

Some updates in the documentation for the upcoming release.

diff --git a/INSTALL b/INSTALL index cf44dc2..3dcbfe2 100644 --- a/INSTALL +++ b/INSTALL @@ -8,6 +8,7 @@ Axel Neumann (neumann-at-notmail.org) Corinna 'Elektra' Aichele (onelektra-at-gmx.net) Thomas Lopatic (thomas-at-lopatic.de) Felix Fietkau (nbd-at-nbd.name) +Ludger Schmudde (lui-at-schmudde.com)

------- @@ -18,8 +19,8 @@ This is still a experimental piece of code to test the viability of the B.A.T.M.A.N routing algorithm based on initial ideas of Thomas Lopatic and Corinna 'Elektra' Aichele.

-This is implementation 0.1-rc0 of the improved B.A.T.M.A.N-III algorithm. It -is not unlikely that we have to fix some bugs. +This is implementation 0.1-rc6b of the improved B.A.T.M.A.N-III algorithm. It +is not unlikely that we still have to fix some bugs.

Use - like always - at your own risk!

@@ -29,8 +30,6 @@ Features --------

Improved B.A.T.M.A.N-III algorithm -Free-BSD support -Mac OS-X support IP-Tunnels via UDP Gateway classes Multiple Interfaces support @@ -42,7 +41,10 @@ dimensional or three dimensional topology graphs. Roadmap -------

-Testing, improvements in the documentation. +Testing, improvements in the documentation. + +Support for Free-BSD and Mac OS-X is broken at the moment since we +introduced UDP-Tunnels - we hope this will be fixed in the near future.

Develop B.A.T.M.A.N-Advanced that routes on Layer 2 and creates a Link-Local-Illusion for higher OSI-Layers @@ -56,8 +58,6 @@ Requirements ------------

Linux with kernel-module 'tun' loaded if you want to use/be a gateway -FreeBSD -MacOS-X

------------ Installation @@ -79,6 +79,23 @@ Note there is no installation script at the moment. If you want to install it, copy the deamon to a location somewhere in your path, for example /usr/sbin or /usr/local/bin.

+If you use a wireless router based on Freifunk-Firmware or OpenWRT you can +use the ipkg-package management system. Add the line: + +src lui http://freifunk.schmudde.com/ipkg + +to your package sources and update the list of available packages by +executing: + +ipkg update + +ipkg install batman-iii + +If you use Freifunk-Firmware you can use the web user-interface for +b.a.t.m.a.n: + +ipkg install batman-iii +

--- @@ -142,6 +159,20 @@ Usage: batman [options] interface [interface interface] -o orginator interval in ms default: 1000, allowed values: >0

+ Note: By default B.A.T.M.A.N keeps track of packets received in the + last 60 seconds (this is called sliding window size). B.A.T.M.A.N + will perform it's routing decisions based on statistics about 60 + packages for a node with an orginator interval of one second. If a + node manages to send us at least 1 message in 60 seconds, it will be + in our routing table. If the orginator interval is increased to 3 + seconds only 20 packets will be kept in the B.A.T.M.A.N statistic - + thus the node must manage to send us 1 out of 20 packets to be in + our routing table. If the sliding window size has more space for + orginator messages the range of multi-hop links will be longer and + therefore weaker routes will find their way into the routing table. + And vice versa. + + -p preferred gateway

This will set up an IP-Tunnel to the destination IP @@ -186,6 +217,11 @@ IP-address within another network:

ifconfig wlan0:0 103.30.30.30 netmask 255.0.0.0 broadcast 103.255.255.255

+The ifconfig command may not be available on your system. To perform the +same operation using the command provided by iproute2: + +ip addr add 103.30.30.30/8 dev wlan0 label wlan0:0 + ./batman -o 2000 wlan0:0

Now you can check out which protocol works better. diff --git a/README b/README index 3f2465a..5d96233 100644 --- a/README +++ b/README @@ -6,18 +6,19 @@ BETTER APPROACH TO MOBILE AD-HOC NETWORKING # 1.) INTRODUCTION # ####################

-B.A.T.M.A.N is a new approach to Ad-Hoc-Routing, unlike other -algorithms that we are aware of. Reactive MANET protocols search for -routes when a node initiates communication to a remote node. Proactive -protocols (link-state algorithms) calculate routes proactively from all -nodes to all nodes in the mesh-cloud, whether they are necessary or -not. B.A.T.M.A.N doesn't calculate routes - it continuously detects -the existence of routes by forwarding and receiving broadcast -packets. The algorithm does not try to find out which path packets -follow to a remote node. B.A.T.M.A.N merely checks which single hop -neighbor it has to send a package to in order to push it on the best -way to a node in the mesh. If you want to find out how B.A.T.M.A.N -routes to a certain node, perform a +B.A.T.M.A.N is a new approach to Ad-Hoc-Routing, unlike other algorithms +that we are aware of. Reactive MANET protocols search for routes when a node +initiates communication to a remote node. Proactive protocols (all +link-state algorithms and some distance-vector algorithms) calculate routes +proactively from all nodes to all nodes in the mesh-cloud, whether they are +necessary or not - while reactive protocols search for routes on demand. +B.A.T.M.A.N doesn't calculate or search for routes - it continuously detects +the existence of routes by forwarding and receiving broadcast packets, and +it proactively populates the routing-table with nodes in the mesh. The +algorithm does not try to find out which path packets follow to a remote +node. B.A.T.M.A.N merely checks which single hop neighbor it has to send a +package to in order to push it on the best way to a node in the mesh. If you +want to find out how B.A.T.M.A.N routes to a certain node, perform a

ping -R <destination address>