From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: [B.A.T.M.A.N.] policy routing improved
Date: Sun, 30 Dec 2007 18:06:12 +0100 [thread overview]
Message-ID: <200712301806.13081.lindner_marek@yahoo.de> (raw)
Hi,
after several talks with different batman users / freifunk communities it
became clear that we need more flexibility for the policy routing. Therefore
I implemented a new option which takes a path to a executable / shell script
as argument (--policy-routing-script). If this option is given batmand will
send all routing table changes to this executable instead of manipulating the
routing table itself. The messages contain all neccessary information to
manipulate the routing table correctly. The executable can modify the
parameters before changing the routing table (routing tables, interfaces,
priorities, etc) or just ignore messages.
I wrote a sample shell script which you can use as basis for your hacking:
http://downloads.open-mesh.net/batman/useful-scripts-and-tools/policy_routing_script.sh
This makes the --no-policy-routing option obsolete which was removed.
Feedback is welcome. ;-)
Greetings,
Marek
reply other threads:[~2007-12-30 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200712301806.13081.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox