From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] My proposed network - is it ok?
Date: Thu, 20 Nov 2008 11:48:41 +0800 [thread overview]
Message-ID: <200811201148.45976.lindner_marek@yahoo.de> (raw)
In-Reply-To: <37878.149.5.32.200.1227142313.squirrel@www.rivertowermail.com>
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
next prev parent reply other threads:[~2008-11-20 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 0:13 [B.A.T.M.A.N.] My proposed network - is it ok? Derek C
2008-11-20 0:51 ` Derek C
2008-11-20 3:48 ` Marek Lindner [this message]
2008-11-20 9:27 ` Derek C
2008-11-20 10:19 ` Marek Lindner
2008-11-20 11:06 ` Derek C
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=200811201148.45976.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox