public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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: Re: [B.A.T.M.A.N.] 0.3 final <-> quagga
Date: Wed, 7 May 2008 20:41:53 +0800	[thread overview]
Message-ID: <200805072041.54021.lindner_marek@yahoo.de> (raw)
In-Reply-To: <51B22798-78A8-4425-BAEA-530297B1518A@cslab.ece.ntua.gr>


Hi,

> I have made a new version of the patch posted by acinonyx (rv502),
> for interfacing batmand with the zebra routing daemon. There are 2
> versions available: One for the latest svn (rv1060) and one for the
> stable 0.3 release. Take a look at:
>
> http://www.cslab.ece.ntua.gr/~chazapis/batman/

it looks good - thanks for your work. I would like to put your changes on 
open-mesh.net. Either linking to your webspace or copying your work on our 
server. What do you prefer ?


> What the patch does is:
> - Adds a flag "-z" to the batmand executable which may be used to
>    enable zebra communication and accepts as an argument the
>    path to the corresponding zebra unix-domain socket.
> - If zebra is enabled:
>    - No rules are added to the kernel.
>    - All UNICAST routes are sent to zebra.

Did you consider using the "--policy-routing-script" for this communication 
with zebra ? You could write an external program that gets the information 
from batman and relays them to zebra. Therefore, you would not need to patch 
every batman installation and would not have to change your patches every 
time when batman changes. By using this facility you can decide what routes 
are sent to zebra, what routes are added to the routing table and you don't 
need to worry about batman. This communication interface could also be used 
by other routing protocols without the need of reinventing the wheel over and 
over again.

Greetings,
Marek

  reply	other threads:[~2008-05-07 12:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 12:17 [B.A.T.M.A.N.] 0.3 final <-> quagga Antony Chazapis
2008-05-07 12:41 ` Marek Lindner [this message]
2008-05-07 13:00   ` Antony Chazapis
2008-05-07 13:29     ` Marek Lindner
2008-05-07 14:10       ` Antony Chazapis
2008-05-07 13:49 ` Daniel Paufler
2008-05-07 14:03   ` Marek Lindner
2008-05-07 16:17     ` Daniel Paufler
2008-05-08  9:23       ` Marek Lindner
2008-05-08  9:18         ` Daniel Paufler
2008-05-08 10:12           ` Marek Lindner
2008-05-12 22:26             ` Antony Chazapis
2008-05-13  8:34               ` Marek Lindner
2008-05-13  9:14                 ` Antony Chazapis
2008-05-14 13:51                   ` Antony Chazapis
2008-05-14 18:52                     ` Marek Lindner
2008-05-15  0:01                       ` Antony Chazapis
2008-05-15  2:12                         ` Marek Lindner
2008-06-11 15:45                     ` Marek Lindner

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=200805072041.54021.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