Wechseln zu: Navigation, Suche

general stuff

  • IP-Range:
  • server

openvpn server. more in a few minutes.

how to setup


  • install openvpn
  • get clientn.crt and clientn.csr from
  • get
  • get
  • unzip client config and ca.crt
  • put everything to /etc/openvpn
  • in /etc/openvpn/client.conf change:
    • cert client.crt
    • key client1.key
  • start openvpn with /etc/init.d/openvpn start
  • check /var/log/syslog for error messages
  • try traceroute to, it should go throug the tunnel
  • check with tcpdump, whether you see olsr packages (hint: they are udp broadcast on port 698)



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 DESTDIR=targetdir. To use other compilers set CC=yourcompiler.


Download OLSRDaemon from

* why such an old olsrd and not ?

build and install

To build:


To install(as root):

make install

To make plugins (needed)

make libs

To install plugins

make install_libs

To delete object files run:

make clean

Optionally, to clean all generated files:

make uberclean

basic config

Before running olsrd you must edit the default configuration file /etc/olsrd.conf adding at least what interfaces olsrd is to run on (in this case is Vpn Tunnel interface Tap0)

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!


To run olsrd just type:

olsrd -f /etc/olsrd.conf

If debug level is set to 0 olsrd will detach and run in the background, if not it will keep running in your shell:

olsrd -f /etc/olsrd.conf -d #

where # = 0..7

Now you can open a tunnel to Freifunk with this command:

openvpn /etc/openvpn/client.conf

After some time, 1-3 minutes, you should be able to see lots of routes with

netstat -rn


http info

The http info plugin gives information via a small embedded http server.

It should be enabled by default and listen on

Configuration is done below the line

LoadPlugin ""

in /etc/olsrd.conf

dot plugin

The dot plugin gives a topology graph in the dot format, which is used by graphviz.

it's output is also needed for freimap.

For minimal configuration, insert following into olsrd.conf:

LoadPlugin ""

To test, do a

telnet 2004

and you should get dot output.

there is a small perl script in lib/dot_draw/misc to draw the topology.

nameservice plugin

The name is a bit misleading, as it has grown from a bit nameservice to be a instrument for flooding many information in the mesh:

  • my hostname
  • hostnames in my attached network
  • address of my dns server
  • geopositions
  • mac addresses
  • services

minimal config:

LoadPlugin ""
        PlParam "name" "demovpn.olsr"
        PlParam "lat" "52.524"
        PlParam "lon" "13.31"
        PlParam "latlon-file" "/var/run/latlon.js"


Please change lat and lon according to your place, it does not need to be super precise in you case but it would be very nice if its at least pointing to your city.

mdns plugin

The mdns plugin relays mDNS (aka bonjour, avahi, howl, ...) through the mesh via the flooding mechanisms provided by olsr.

It has been developed by

How it works

To discover services in the network applications exchange multicast DNS packets. This means that we are able to discover services offered in the network within our multicast domain. In a wireless mesh network, the usage of wireless interfaces in ad-hoc mode and the OLSR routing protocol prevent multicast messages to be distributed all over the network. The key idea is to extend the multicast domain of the networks that do not directly partecipate in the OLSR mesh cloud but that are fully routable and announced via HNA.

This task is achieved in the following way: 1. the local router picks up from the local non-OLSR (HNA) network mDNS messages and encapsulates them in a new type of OLSR messages 2. the OLSR infrastructure is exploited for the transport of these messages 3. remote routers decapsulate mDNS messages from received OLSR messages and send them over their attached non-OLSR networks.

The plugin captures the traffic (only IPv4 if OLSR is running IPv4 and only IPv6 if OLSR is running IPv6) and encapsulates this traffic in OLSR messages that are forwarded to all the other nodes in the mesh.

Other nodes running the plugin will decapsulate the packets and will send them to the interfaces specified in the configuration file.


For minimal configuration add these lines to olsrd config file:

LoadPlugin "" 
           PlParam     "NonOlsrIf"  "eth0" 
           PlParam     "NonOlsrIf"  "eth1" 

Where eth0 and eth1 are the names of the interfaces where you want to capture traffic (and decapsulate incoming traffic).

Note that this interfaces MUST NOT talk OLSR and also the subnets on this interfaces must be announced with an appropriate HNA entry.

To receive mDNS messages on an host running olsrd, then put "lo" as NonOlsrIf.


freimap is our central tool for data acquisition and visualisation.



  • git (git-core)
  • java (sun-java6-jdk)



git clone git://


cd into src dir



create config.yaml:

version: svn
subversion: 60

    type: openstreetmap
    # use blank, images or openstreetmap
    delay: 0
    filter: dark
    cachedir: ./gfx/cache

    class: net.relet.freimap.LatLonJsDataSource
    url: "file:/var/run/latlon.js"

    class: net.relet.freimap.OlsrdDataSource
    host: localhost
    port: 2004
    nodesource: nodes-in-berlin