From: Bjoern Franke <bjo@nord-west.org>
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: loop caused by tinc and wifi
Date: Tue, 27 Sep 2011 12:45:01 +0200 [thread overview]
Message-ID: <1997296.MKzYFvRXTH@mytilus> (raw)
In-Reply-To: <201109261726.38951.lindner_marek@yahoo.de>
Am Montag, 26. September 2011, 17:26:37 schrieb Marek Lindner:
> On Monday, September 26, 2011 14:33:57 Bjoern Franke wrote:
> > We did not enable bridge loop avoidance, IIRC we did not run batman on
> > the bridge interface due to overhead on the vpn links.
> >
> > But we'll enable it on the nodes we have access to.
>
> Please give it a try. It sounds like a bridge loop.
Ok, we have running now the following setup:
ath1 (ad-hoc) as batman-interface
br-mesh (ath0 (ap-mode), eth0.1, tap0, bat0) as batman-interface
batman complains about the mtu 1500 of br-mesh, but it can't be set to 1527
because bat0 does not like any mtu setting.
> We are working towards an enhanced bridge loop mechanism which aims to
> reduce the overhead. Are you interested in testing it when it gets ready ?
>
Yes, this would be nice :)
regards
Bjoern
--
jabber: bjo@schafweide.org
bjo.nord-west.org | nord-west.org | freifunk-ol.de
next prev parent reply other threads:[~2011-09-27 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 0:15 [B.A.T.M.A.N.] batman-adv: loop caused by tinc and wifi Bjoern Franke
2011-09-26 7:05 ` P. Mazart
2011-09-26 9:15 ` Bjoern Franke
2011-09-26 9:36 ` Marek Lindner
2011-09-26 12:33 ` Bjoern Franke
2011-09-26 15:26 ` Marek Lindner
2011-09-27 10:45 ` Bjoern Franke [this message]
2011-09-27 11:44 ` Marek Lindner
2011-09-27 22:03 ` Bjoern Franke
2011-09-29 10:08 ` Marek Lindner
2011-09-29 13:51 ` Bjoern Franke
2011-09-29 20:25 ` Bjoern Franke
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=1997296.MKzYFvRXTH@mytilus \
--to=bjo@nord-west.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.