From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <97C5B1C7CD044FEDB67CC3C1E2055BDD@flightrisk> References: <201009262057.36382.lindner_marek@yahoo.de> <1285527477-10340-1-git-send-email-lindner_marek@yahoo.de> <201009261516.21774.lew.pitcher@digitalfreehold.ca> <97C5B1C7CD044FEDB67CC3C1E2055BDD@flightrisk> Date: Mon, 27 Sep 2010 14:22:52 +1300 Message-ID: From: Donald Gordon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [B.A.T.M.A.N.] batman-adv: softif lan loop avoidance 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 Mon, Sep 27, 2010 at 1:25 PM, DuncanSF wrote: > Doing this defeats part of the purpose of running batman-adv on > a LAN. =A0Picture the case where nodes have links between each > other both on their wireless interfaces and through Homeplug > adapters like the old Netgear XE102 Ethernet-to-Powerline bridge. > > Electing a single mesh-to-LAN gateway as proposed will blackhole > any stations on that LAN unable to reach the elected gateway. > > Not everything connected to a LAN port is a standard, reliable > local area network. =A0*smiles* Surely in that situation you'd run batman-advanced in a topology where you only sent batman-encapsulated packets over your unreliable ethernet (which is unreliable in a similar way to adhoc wifi), and then either configure up your bat0 interfaces locally on every host or bridge the bat0 interfaces to nice reliable local ethernet networks. Then batman would automatically choose the best path over the available networks to connect your islands of reliability :-) donald