All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Rack <michael.rack@rsm-freilassing.de>
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.] Problems with Gateway-Selection without option -g
Date: Sun, 06 Sep 2009 13:33:22 +0200	[thread overview]
Message-ID: <4AA39E02.7030201@rsm-freilassing.de> (raw)
In-Reply-To: <200909061250.40558.onelektra@gmx.net>

Hi Elektra,

thanks for your trick. This trick works for me, but it is a bad solution 
:-) I switched back to OLSR, although i like the concept of BATMAN more 
then that of OLSR.

Announcing 0.0.0.0/0 can really be a problem, but why does BATMAN tunnel 
the internet-traffic through gate0?

It will be nice, if there will be a option in the next release, where 
users can decide to use routing or tunneling internet-traffic.

Cheers,
Michael.

Am 06.09.2009 12:50, schrieb elektra:
> Hello Michael!
>
> Batmand checks and deliberately blocks users from announcing 0.0.0.0/0 - this
> could cause the notorious black-hole problem we have experienced in the old
> days when using OLSR. Also we think it is important that we can explicitly
> tell a Batman node to use Internet gateway functionality or not.
>
> Default routes in a mesh can be really annoying and break network
> functionality. If you only have one default gateway in your Batmand network
> and really know what you are doing you can actually override this check with a
> simple trick.
>
> As a workaround you can announce two subnetworks 0.0.0.0/1 and 128.0.0.0/1
> instead of 0.0.0.0/0.
>
> batmand -a 0.0.0.0/1,128.0.0.0/1<your interface>
>
> Cheers,
> Elektra
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@lists.open-mesh.net
> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n


  reply	other threads:[~2009-09-06 11:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-06  5:28 [B.A.T.M.A.N.] Problems with Gateway-Selection without option -g Michael Rack
2009-09-06 10:50 ` elektra
2009-09-06 11:33   ` Michael Rack [this message]
2009-09-06 12:37     ` elektra
2009-09-06 15:11 ` Marek Lindner
2009-09-06 17:13   ` Michael Rack
2009-09-06 17:47     ` Marek Lindner
2009-09-07 10:16       ` Michael Rack
2009-09-07 13:02         ` Marek Lindner
2009-09-07 13:40           ` Michael Rack
2009-09-08 17:57             ` Marek Lindner
2009-10-30 10:19               ` Michael Rack
2009-10-30 12:11                 ` 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=4AA39E02.7030201@rsm-freilassing.de \
    --to=michael.rack@rsm-freilassing.de \
    --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.