From: rene <batman@absorb.it>
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.] single IP for multiple interfaces
Date: Tue, 20 Nov 2007 17:09:22 +0530 [thread overview]
Message-ID: <4742C76A.6050404@absorb.it> (raw)
In-Reply-To: <200711201232.11894.axel@open-mesh.net>
Hi,
Axel Neumann wrote:
>>> There MUST be a different IP address for each BATMAN interface in the
>>> network (also if a single BATMAN node has more than one interface).
>> Is this implemented like this (where?)?
> Yes it is implemented/designed like this. It operates on layer three and
> above. IP addresses are used to differentiate between different links to the
> same neighbors. For example two nodes A and B, each with two wireless
> interfaces 1 and 2. All interfaces operating in the same channel, bssid, ...
> How could node A differentiate between the link A1<->B1 and A1<->B2 if it is
> not aware of any MAC addresses. But even if it is aware of MAC addresses. How
> could it set up the routing table to ensure that a packet to a distant node C
> should be routed via B1 (and NOT via B2)?
just by setting the interface to the way the package has to leave the
node? Just the same way olsr does, I'm not a protocol designer but don't
see any main reason why Batman shouldn't be possible to do it similar.
> Actually, I did not even know that this is possible - is such a configuration
> proposed somewhere. I can imagine that this somehow works but how shure are
> you that this does not introduce any negative side effects?
We are using this in Rostock since a while (on all WRAPs and on selected
APs) and it works very well. Side effects? Maybe, you never know for
sure, none recognized and I'm not deep enough into protocol designs to
answer this from a theoretical point of view. But it's a great feature
which makes Mesh networking much easier and the whole structure much
cleaner.
Regards,
Rene
next prev parent reply other threads:[~2007-11-20 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 5:22 [B.A.T.M.A.N.] problem starting batmand (v799) rene
2007-11-20 9:08 ` Axel Neumann
2007-11-20 10:31 ` rene
2007-11-20 10:59 ` [B.A.T.M.A.N.] single IP for multiple interfaces (was: Re: [B.A.T.M.A.N.] problem starting batmand (v799)) Marek Lindner
2007-11-20 11:29 ` [B.A.T.M.A.N.] single IP for multiple interfaces rene
2007-11-20 12:24 ` Marek Lindner
2007-11-20 13:45 ` rene
2007-11-20 14:08 ` Marek Lindner
2007-11-20 11:32 ` [B.A.T.M.A.N.] problem starting batmand (v799) Axel Neumann
2007-11-20 11:39 ` rene [this message]
2007-11-20 12:31 ` [B.A.T.M.A.N.] single IP for multiple interfaces Axel Neumann
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=4742C76A.6050404@absorb.it \
--to=batman@absorb.it \
--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