All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Paufler <dpaufler@leo34.net>
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, 07 May 2008 18:17:46 +0200	[thread overview]
Message-ID: <4821D62A.4010705@leo34.net> (raw)
In-Reply-To: <200805072203.33919.lindner_marek@yahoo.de>


[-- Attachment #1.1: Type: text/plain, Size: 1325 bytes --]

Hey Marek

Marek Lindner wrote:
>> I am mainly interested in redistributing zebra routes to batman as i do
>> with olsr_quagga plugin. This way, i can think about switching from olsr
>> to batman 0.3. Perhaps, you will enable it in your code again.
> it was never "enabled" - it was part of a patch.
> I'm not that familiar with zebra/quagga. Can you explain what you need and why 
> the dynamic HNA adding/deleting is not enough ? That feature did not exist in 
> revision 502.
Enabling zebra to tell batmand to add/remove routes needs a patch in
zebra. It would be really nice to have a batmand plugin whatever that
talks to zebra for getting dynamic HNA routes. So i dont have to modify
my zebra, but can enable a plugin in batmand (as it is in OLSR).

I need this for BGP routing. Imagine to route two batmand clouds
together via BGP. If the third cloud joins, i dont want to reconfigure
the other batmand-daemons. They just grep the routes from the running zebra.

Another big option would be to let zebra speak batman / olsr protocol
and be able to configure batman / olsr through zebra interface /
configuraion. But that would be "top of everything" and imo not necessary.

Greetz

Daniel

-- 
Dipl. Inf. (FH) Daniel Paufler
Angewandte Informatik - Computer Aided Facility Management



[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2008-05-07 16:17 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
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 [this message]
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=4821D62A.4010705@leo34.net \
    --to=dpaufler@leo34.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.