From: "L. Aaron Kaplan" <aaron@lo-res.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] What routingprotocol is similar to B.A.T.M.A.N ?
Date: Wed, 25 Nov 2009 12:09:35 +0100 [thread overview]
Message-ID: <4B0D106F.40404@lo-res.org> (raw)
In-Reply-To: <4B0D0DD2.1040107@rsm-freilassing.de>
Michael Rack wrote:
> Dear List,
>
> sorry if that is not the right place for my question. But the approach
> of B.A.T.M.A.N in how to choise the next hop is phantastic. Protocols
> how BGPv4 and OSPF only take the shortest path to the destination.
> B.A.T.M.A.N looks for the fastest way where the Hello-Message arrives
> first.
>
> So long. I need a Routing-Protocol for static mash. My
> Wireless-Network besides on fixed Wireless Stations they become never
> to be dynamic. The complete Wireless Network is in
> Infrastructure-Mode. All members in the Network have just one role (AP
> / Client).
>
> Currently OLSR does the routing job. But there lots of problems. OLSR
> also take the shortest path, also in case, a better link is available.
>
For OLSR development it would be interesting if you could discuss on the
mailing list there how your routing metric should be.
OLSR has a very nice framework (this is one of the advantages that it
has next tom some disadvantages) that actually you *can* change the metric!
We simply did not find any way yet to make layer 2 metrics cross
plattform comparable.
But this is better discussed on the OLSR mailing lists of course. (off
topic here)
> B.A.T.M.A.N is not suitable for my situation. The Client should not be
> able to select a desired gateway. A gateway should inject a default
> gateway to the clients, how OLSR does it.
>
> Is there any other routing protocol on the market, that combine all
> that features, that i need?
>
You could try BGP . It is for sure very stable and very well tested ;-)
And actually it is also used in static mesh networks.
I have the feeling that it will actually do what you want. without major
bugs.
> * Routing descission on fastest HelloMessage
> * Inject Default-Gateway via 0.0.0.0/0
> * Without tunneling data
>
> Liebe Grüße aus Freilassing,
>
> Michael Rack
> RSM Freilassing
next prev parent reply other threads:[~2009-11-25 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 10:58 [B.A.T.M.A.N.] What routingprotocol is similar to B.A.T.M.A.N ? Michael Rack
2009-11-25 11:09 ` L. Aaron Kaplan [this message]
2009-11-25 13:58 ` elektra
2009-11-25 14:02 ` L. Aaron Kaplan
2009-11-25 14:49 ` [B.A.T.M.A.N.] Protocol quarrels elektra
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=4B0D106F.40404@lo-res.org \
--to=aaron@lo-res.org \
--cc=b.a.t.m.a.n@lists.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