public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Vinay Tharigopula <vinay@orxrail.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] batman-adv mesh slows down wired clients (bridge-loop-avoidance)
Date: Thu, 24 Feb 2011 12:02:55 -0500	[thread overview]
Message-ID: <4D668F3F.4080700@orxrail.com> (raw)

Hello..

I succesfully configured a batman-adv mesh to add access points to our 
existing wired lan.  I am using Openwrt 10.04 and batman-adv 2010.1.0. 
DHCP and everything works as expected. Any wired or wireless client 
connecting to the network gets an IP from a DHCP server hooked into the 
switch etc etc.

Our Network configuration:

8 batman-adv routers with a wireless mesh  with two or more of the 
routers having a wired connection directly to the switch. In this case, 
the 8 routers decide to pick one of the "plugged in" routers as a 
gateway to avoid bridge loops. This is fine.

I have been running into issues with wired clients however.

When a wired client plugged into the switch tries to contact a wired 
client plugged into the same switch, the packets manage to get lost. I 
believe they are are going through the wireless routers plugged into the 
same switch.

Instead of going like this..

PC 1 ----> switch1 ---> PC 2

they seem to be going like this... (my guess).

PC 1 ---> switch1 ---> wireless router 1 ----(wireless mesh link)----> 
wireless router 2 ----> switch1 --->  PC 2.

I think this is because the translation tables on the bat node are 
announcing that even the wired clients are connected to them.

This is causing extreme delays even in wired clients. Any help will be 
appreciated. Should I enable STP in on the switch ports ?

- Vinay

             reply	other threads:[~2011-02-24 17:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 17:02 Vinay Tharigopula [this message]
2011-02-24 19:44 ` [B.A.T.M.A.N.] batman-adv mesh slows down wired clients (bridge-loop-avoidance) 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
  -- 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=4D668F3F.4080700@orxrail.com \
    --to=vinay@orxrail.com \
    --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