From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Lindner Subject: Re: [B.A.T.M.A.N.] My proposed network - is it ok? Date: Thu, 20 Nov 2008 11:48:41 +0800 References: <52133.149.5.32.200.1227140000.squirrel@www.rivertowermail.com> <37878.149.5.32.200.1227142313.squirrel@www.rivertowermail.com> In-Reply-To: <37878.149.5.32.200.1227142313.squirrel@www.rivertowermail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811201148.45976.lindner_marek@yahoo.de> 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 Hi, > I've been trying to test this idea a bit but I'm a bit concerned - does > BATMAN only work with AdHoc wireless NICs? no - its does not care about the lower layers. It will run on ad-hoc, managed, ethernet, etc ... Batman also runs on multiple interfaces. Simply supply several interfaces on the command line: batmand if1 if2 if3 > I have a server with an Ethernet NIC with an IP 5.0.0.1/8. I've got a > transparent AP bridge with an IP of 5.1.0.1/8 and normally I can ping it > from my server. > > Maybe this is due to an IP2 rule/route? I can see that this is due to a > IP2 rule "from all to 5.0.0.0/8 lookup 67" and routes for table 67 is > "unreachable default proto static" Yes, the unreachable route may be the reason for that. Batman assumes that everything within its own IP range (5.0.0.1/8) should have a routing entry or the route does not exist. It lets you detect faster whether a node is down or not. Depending on your setup it may make sense to not have a route. Does the AP bridge (5.1.0.1/8) have a route back to your server ? If you want to integrate batmans routing decision into your fancy setup have a look here: https://dev.open-mesh.net/batman/wiki/RoutingVodoo Marek