From: "Linus Lüssing" <linus.luessing@web.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Mesh network topology problem
Date: Wed, 5 Jan 2011 11:57:47 +0100 [thread overview]
Message-ID: <20110105105747.GA6723@Sellars> (raw)
In-Reply-To: <E056F038D9D24718AF5E3AFDC7E7BAEE@granch.local>
Hi Michael,
Welcome to the BATMAN mailing list :). Let me ask some general
questions first about what you're trying to achieve. So you are
trying to set up a highly fault tolearant network. Does the
fault tolerant setup have any time limitations, how quickly do you
need to detect outageous and switch? So far it looks like you're
having just a wlan0 interface inside of batman-adv, right?
So you usually want to use the wired links but use the wireless mesh
network as a backup?
Could you explain the picture you've attached a little further. I
guess (1) - (8) and (11) - (18) are nodes which are running
batman-adv, what are (CCbs0/1)? Do blue lines represent the wired
links attached to a switch (so 4 switches involved?) and a thin black
line the wifi-links? What is a thick black line, what do the numbers represent?
On Mon, Jan 03, 2011 at 03:24:45PM +0600, Michael Y. Gluhovchenko wrote:
> Hello All;
>
> I have a problem organizing mesh, each wireless router has a Wifi
> link and 2 wired links. The problem is that there is the parallel
> corridor with the same infrastructure. Routers can see each other
> across the corridor, the signal quality in the corridor is better
> than the main line.
> I want to use Linux bridge + stp interfaces bat0, eth0, eth1 wired
> links have advantages. When break wire links or failure one of the
> routers need to maintain communication through the mesh. Is it
> possible to configure mesh so that the link in another corridor with
> the best quality work in the last turn?
Are you talking about a wireless link here? Which link are you
refering to here exactly?
> What problems can occur for
> that network topology.
Well, if done wrong, bridge-loops ;). I think with stp and
bridging the wifi-mesh and wired network would be one possible
solution, but there are at least two more ways to go. It would be
great if you could explain the physical network topology a little
more with the help of the picture so that we'd be able to better
decide which of those solutions might be most suitable for you.
>
> With best regards,
> Michael;
Cheers, Linus
PS: Also note, that STP over batman-adv will create quite some
overhead, depending on the number of nodes you are running.
batman-adv will flood each STP packet through the whole
wireless mesh.
next prev parent reply other threads:[~2011-01-05 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 9:24 [B.A.T.M.A.N.] Mesh network topology problem Michael Y. Gluhovchenko
2011-01-05 10:57 ` Linus Lüssing [this message]
2011-01-05 12:52 ` Michael Y. Gluhovchenko
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=20110105105747.GA6723@Sellars \
--to=linus.luessing@web.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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