public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Daniel Poelzleithner <poelzi@poelzi.org>
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.] Multiple connections / prioritiy
Date: Tue, 24 Jul 2007 07:44:32 +0200	[thread overview]
Message-ID: <46A591C0.8090009@poelzi.org> (raw)
In-Reply-To: <20070723140744.ozvor890jy5cockg@webmail.ddmesh.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Freifunk Dresden wrote:

> If I have multiple connections between two nodes, is there a way to
> setup the quality or
> priority of those connection?

Same goes for Leipzig, we have our vpn[1,2].leipzig.freifunk.net nodes.
I thought about this problem a lot and the simplest solution would be to
simply drop like 9 of 10 batman packets on the outgoing vpn interface.
this is like a olsr multiplicator of 10 with the advantage that it saves
bandwith.

short anecdote about dropping olsr packets:
so, we now have this huge vpn that connects most edges of the mesh to
central olsr nodes. because this are just backup routes, we have to
increase the etx value, no problem with the olsr multiplier option. on
the vpn a packetloss of 0% ist relative normal, so you pump out 5kb/s of
olsr traffic just to say: mmhh, ok, very good connection but i think its
bad anyway. so, if olsr messures the packet loss rate, i could simply
drop 9 of 10 packets and with 0.5kb/s i would have the same effect. if
that is what olsr is supposed to do.

by the way, we have arround 400 GB per month olsr overhead alone, which
is just creazy for a routing protocol overhead.

i ran a couple of tests.
there is a iptables match called nth, so i tested to allow only every
tenth packet. i got a etx of 0.0
strange: i allowed 50% -> etx 0.0
stranger: i allowed 90% -> etx 0.0
there is a percent match. i combined them, i tried percent alone, etc.
olsr depends a lot about which packets get dropped.
you simply can't just drop packets without getting etx 0.0 for at least
periods of 20-30 seconds, which drives you nuts.

batman should work very well with that approach.

kindly regards
 Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: GnuPT 2.7.2
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGpZG/y/mkIQp7AD0RAtcUAKDPP/rKGgMt5doPyLdgxcDPm1cO/QCgsQ09
kXCustGVyorDABZKxXlutWk=
=BXOc
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-07-24  5:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 12:07 [B.A.T.M.A.N.] Multiple connections / prioritiy Freifunk Dresden
2007-07-24  5:44 ` Daniel Poelzleithner [this message]
2007-07-24 10:54   ` Axel Neumann
2007-09-03 16:21   ` 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=46A591C0.8090009@poelzi.org \
    --to=poelzi@poelzi.org \
    --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