All of lore.kernel.org
 help / color / mirror / Atom feed
From: elektra <onelektra@gmx.net>
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 14:58:45 +0100	[thread overview]
Message-ID: <4B0D3815.9020104@gmx.net> (raw)
In-Reply-To: <4B0D106F.40404@lo-res.org>

Hello Michael -


this question frequently pops up on this list.

You can use layer 3 Batman to announce a default route, but this is not 
recommended. Default routes in a large mesh are a pain in the ****. 
Which is something we quickly realized in the Freifunk community as soon 
as we had more than one gateway or malfunctioning gateways  - those will 
act as black holes and effectively interrupt your service.

You can circumvent the 0.0.0.0/0 check in Batman, by announcing two 
HNA's of 0.0.0.0/1 and 128.0.0.0/1 with the -a option. If you don't 
define a gateway class on the gateway the Batman gateway clients can't 
select a gateway.

Disadvantages: Other than the fact that I personally consider the 
announcement of 0.0.0.0/0 routes as sabotage - none that I know of, 
really. A few bytes overhead in the OGMs of the gateway, thats it.

We have occasional OLSR advertisement fade-ins on this list - I guess 
the Babel/OLSR/Batman quarrel will become proverbial one day ;-)

Cheers,
Elektra



  reply	other threads:[~2009-11-25 13:58 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
2009-11-25 13:58   ` elektra [this message]
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=4B0D3815.9020104@gmx.net \
    --to=onelektra@gmx.net \
    --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 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.