Return-Path: From: elektra Date: Sun, 6 Sep 2009 12:50:40 +0200 References: <4AA34865.9000203@rsm-freilassing.de> In-Reply-To: <4AA34865.9000203@rsm-freilassing.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200909061250.40558.onelektra@gmx.net> Subject: Re: [B.A.T.M.A.N.] Problems with Gateway-Selection without option -g Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking 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 Cheers, Elektra