Here is the patch that adds a package for The BIRD Internet Routing
Daemon. It is updated to the current version of BIRD (v 1.2.2).
BIRD is an internet routing daemon that implements OSPF, RIP and BGP.
It is fast, lightweight and small (cca 300 kB), therefore ideal for
OpenWRT based routers.
The makefile is rather tricky, as BIRD have to be built two times (for
IPv4 and IPv6 versions) and there are separate packages for BIRD daemon
and BIRD client, because client depends on libreadline and is not
strictly necessary.
Signed-off-by: Ondrej Zajicek <santiago@crfreenet.org>
git-svn-id: svn+ssh://svn.openwrt.org/openwrt/packages@20780 3c298f89-4303-0410-b956-a3cf2f4a3e73
the module version which is used by batctl to tell the user which version
batman-adv the node is currently running.
Un-define this constant to prevent the metadata from being stripped
Signed-off-by: Antonio Quartulli <ordex at autistici.org>
Add A.L.F.R.E.D - Almighty Lightweight Fact Remote Exchange Daemon
to the OpenWRT routing feed. This package contains the latest stable
release of alfred which has been recently published by the
open-mesh.org community. A description follows below.
alfred is a user space daemon for distributing arbitrary local
information over the mesh/network in a decentralized fashion. This data
can be anything which appears to be useful - originally designed to
replace the batman-adv visualization (vis), you may distribute
hostnames, phone books, administration information, DNS information,
the local weather forecast ...
alfred runs as daemon in the background of the system. A user may insert
information by using the alfred binary on the command line, or use
special programs to communicate with alfred (done via unix sockets).
alfred then takes care of distributing the local information to other
alfred servers on other nodes. This is done via IPv6 link-local
multicast, and does not require any configuration. A user can request
data from alfred, and will receive the information available from all
alfred servers in the network.
Signed-off-by: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
physical device instead. But only if the protocoll is "static" or "none".
This is useful to write Interfaces in the resulting olsrd.conf file which
are not up at the time olsrd is starting (e.g. tunnel interfaces):
