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@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Route selection over VPN links
Date: Tue, 17 Jul 2012 12:57:23 +0200 [thread overview]
Message-ID: <201207171257.23627.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CAKLmikOuvdvdzV+UD-qr=FSKA0s+1yMHcdYr4GU6S4VzvqcMcw@mail.gmail.com>
On Tuesday, July 17, 2012 08:36:30 Mitar wrote:
> > the later versions of batman support a routing protocol plugin structure
> > (check bat_iv_ogm.c to get an idea). Using bandwidth information for the
> > routing decision is a nice idea but how does your concept look like ? How
> > should the routing logic look like ?
>
> I thought I explained it enough. So for now, I would just go with only
> measuring latency (I don't know what would be the best way to measure
> this, though). If I have the latency (and this could be only one hop),
> I would do:
>
> * if packet loss is different, choose the one with lower packet loss
> * if packet loss is the same, choose the one with lower latency in the next
> hop
I was more curious about the bandwidth routing than the latency stuff. The
current routing algorithm already takes latency into account. An alternate
path always need to be better than the current path. If both paths are equal
the faster packets win the race.
Regards,
Marek
next prev parent reply other threads:[~2012-07-17 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 20:29 [B.A.T.M.A.N.] Route selection over VPN links Mitar
2012-07-16 10:02 ` Marek Lindner
2012-07-17 6:36 ` Mitar
2012-07-17 10:57 ` Marek Lindner [this message]
2012-07-17 18:06 ` Mitar
2012-07-17 18:22 ` Andrew Lunn
2012-07-17 19:29 ` Mitar
2012-07-18 6:43 ` Christian Huldt
2012-07-18 8:15 ` Mitar
2012-07-18 20:06 ` Marek Lindner
2012-07-20 21:14 ` Mitar
2012-07-21 10:12 ` 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=201207171257.23627.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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.