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.] Quagga zebra API client for BATMAN
Date: Wed, 2 Jan 2008 16:14:21 +0100 [thread overview]
Message-ID: <200801021614.22056.lindner_marek@yahoo.de> (raw)
In-Reply-To: <200712310201.49542.acinonyxs@yahoo.gr>
Hi,
> I've added support to send BATMAN routes to zebra daemon and redistribute
> them to other Quagga protocols. The interface is through zebra UNIX socket.
> A new option -q followed by the UNIX socket path is added (see batmand
> --help) to enable route export. I've also implemented a metric for BATMAN
> routes based on TTL value which is essential when using BATMAN as IGP to
> BGP Confederations.
thanks for submitting your work. I published it on our website so that others
can find it: https://www.open-mesh.net/batman/patches
By the way: Using the TTL as basis for a hop metric is ambiguous and may lead
to errors. By doing so you assume that every host uses the same start TTL and
every hop decreases it in the same way. The B.A.T.M.A.N. protocol does not
demand or enforce this behaviour.
On the other hand the hop count does not reflect the quality of a path. May be
it would be a better approach to calculate the link quality into the metric
so that hop based protocols can do a better decission.
Regards,
Marek
next prev parent reply other threads:[~2008-01-02 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 10:48 [B.A.T.M.A.N.] batmand_0.3~r875 debian packages available Holger Levsen
2007-12-27 12:20 ` Simon Wunderlich
2007-12-27 13:41 ` Holger Levsen
2007-12-31 0:01 ` [B.A.T.M.A.N.] Quagga zebra API client for BATMAN Acinonyx
2008-01-02 15:14 ` Marek Lindner [this message]
2008-01-05 11:00 ` Acinonyx
2008-01-18 16:16 ` Acinonyx
2008-01-20 7:52 ` Axel Neumann
2008-01-25 20:50 ` Acinonyx
2007-12-27 12:27 ` [B.A.T.M.A.N.] batmand_0.3~r875 debian packages available Axel Neumann
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=200801021614.22056.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;
as well as URLs for NNTP newsgroup(s).