public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] batman-adv mesh slows down wired clients (bridge-loop-avoidance)
Date: Tue, 1 Mar 2011 03:24:31 +0100	[thread overview]
Message-ID: <201103010324.32398.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4D6BF3B3.8040509@orxrail.com>


Hi,

> I think the List had issues with all of us getting multiple emails for
> some reason. I wanted to update you on this status and let others know
> about my solution.

yes, mailman was standing still due to a deadlock. Sven had to restart mailman 
before all the sent mails were processed. Seems some people were getting 
impatient ..  ;-)


> I had to enable STP on the lan-switches.  STP type: STP and Mode: Root
> Protection. This can be enabled on all ports safely without causing
> disruption to the clients plugged into the switch.
> 
> After this step was done, bridge-loop-avoidance worked properly and if
> more than 1 router in a mesh was plugged in, all the routers would pick
> one as a gateway.

I don't know much about STP (root protection does not tell my anything) but 
using STP seems like a very bad idea. STP does not know a thing about your 
mesh network and the qualities of the links. To avoid the loop it will simply 
turn off "ports" in the router which certainly is not what you want. At some 
point in time it might decide to turn off a port you are using ...

I re-read all the mails but I still can't understand your logic: You have 2 
batman-adv gateways that announce the wired clients via HNA. This happens to 
allow wireless clients connected to the mesh to communicated with your wired 
clients. No problem here. Why do you think the packets go through the mesh ?


> If more than one is plugged in, the higher MAC router will drop all lan
> packets which will result in slower throughput to clients to that router
> because it is hopping to another router via wireless and neglecting the
> fact that it's own wired link would take it faster to the intended
> destination.

Are you talking about the bridge-loop-avoidance ? What makes you think they 
are using the wireless interface to forward the traffic to the other gateway ?


> My "solution" to this was to enable STP in the router too.

Again, using STP on top of batman-adv will create more problems than it 
solves.

Regards,
Marek

  reply	other threads:[~2011-03-01  2:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 17:02 [B.A.T.M.A.N.] batman-adv mesh slows down wired clients (bridge-loop-avoidance) Vinay Tharigopula
2011-02-24 19:44 ` Linus Lüssing
2011-02-24 20:12   ` Vinay Tharigopula
2011-02-25  0:30     ` Marek Lindner
2011-02-25 13:44       ` Vinay Tharigopula
2011-02-25 16:14         ` Vinay Tharigopula
2011-02-25 16:22         ` Vinay Tharigopula
2011-02-25 22:41         ` Linus Lüssing
2011-02-26 19:31         ` Linus Lüssing
2011-02-26 22:49         ` Marek Lindner
2011-02-28 19:12           ` Vinay Tharigopula
2011-03-01  2:24             ` Marek Lindner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-26 23:01 Marek Lindner

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=201103010324.32398.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.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