public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Predrag Balorda <predrag.balorda@gmail.com>
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-beta-rv779 and rv780
Date: Tue, 6 Nov 2007 13:35:53 +0100	[thread overview]
Message-ID: <000301c82071$95051270$bf0f3750$@com> (raw)
In-Reply-To: <200711060915.59594.axel@open-mesh.net>

Thank you for your quick replies guys. I just woke up (doh!) so I'll get
back to you with all details shortly, but just to quickly answer axels
question on olsr.

Ok I will also post my setup

Aa ----------------- Ba --------- Ca  (a is 11a g is 11bg interface)
105.0.0.1/24     105.0.0.2   105.0.0.3
Ag ----------------- Bg --------- Cg
105.0.1.1/24     105.0.1.2   105.0.1.3

11a is switched OFF on all nodes.

OLSR seems to ALWAYS just go from Ag directly to Cg (I presume it's because
it can see it on g radio) even though route through Bg would be better and
it takes 10-15ms (at least for traceroute output). B.A.T.M.A.N ALLWAYS goes
through Bg and it's all 2ms hops Ag > Bg 2ms, Bg > Cg 2ms. Much better
wouldn't you say?
That's why I've given up on OLSR.

Ok that was the short answer, later I'll get back to you on the gate0 issue.

> but I believe this would be a 
> far more usable setup than olsr 5.3 that I also tried.
maybe check 5.4. Because I think that the improvements from 5.3 to 5.4 are 
huge, but also because I am always interested in the concrete pros and cons 
that people observe between the latest olsr/batman state-of-the art.


ciao,
axel


      reply	other threads:[~2007-11-06 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 21:14 [B.A.T.M.A.N.] 0.3-beta-rv779 and rv780 Predrag Balorda
2007-11-06  8:15 ` Axel Neumann
2007-11-06 12:35   ` Predrag Balorda [this message]

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='000301c82071$95051270$bf0f3750$@com' \
    --to=predrag.balorda@gmail.com \
    --cc=b.a.t.m.a.n@open-mesh.net \
    --cc=pele@balorda.com \
    /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