From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Sat, 3 Mar 2012 15:53:53 +0800 References: <4F51CA9D.2090404@codigosur.org> In-Reply-To: <4F51CA9D.2090404@codigosur.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201203031553.53565.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] routing loops on interconnected routers / adhoc + ethernet 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 On Saturday, March 03, 2012 15:39:09 Nicol=E1s Ech=E1niz wrote: > this happens with the nodes configured according to: > http://www.open-mesh.org/wiki/batman-adv/Bridge-loop-avoidance >=20 > or so we understand! If the ethernet is used for mesh purposes uniquely why do you bother runnin= g=20 the bridge loop avoidance at all instead of adding the ethernet interface a= s a=20 regular batman interface ? The only reason why you would want the bridge lo= op=20 avoidance is when you have ethernet clients that are bridged into the mesh.= =20 This does not seem to be the case. As far as I understand the ethernet cabl= e=20 is used as reliable "wireless cable". Cheers, Marek =20