From: "Linus Lüssing" <linus.luessing@c0d3.blue>
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.] Current OpenWrt build
Date: Sun, 16 Nov 2014 07:51:23 +0100 [thread overview]
Message-ID: <20141116065123.GB2469@odroid> (raw)
In-Reply-To: <069201cffe76$c6b720c0$54256240$@dslx.net>
On Wed, Nov 12, 2014 at 07:47:10AM -0500, Jay Brussels wrote:
> Antonio,
>
> I am planning to start programming Ubiquiti and TP-Link Routers in two weeks for a very large BATMAN mesh deployment.
>
> Although many patches I have seen on this list involves multicast traffic I have seen some others.
>
> Is the current OpenWrt release stable enough for deployment or are there some "must have" patches requiring a build from scratch for a successful deployment?
Regarding Barrier-Breaker: The default settings in OpenWRT with
bridges are unfortunately broken (in that breakes multicast, which
means broken IPv6):
https://lists.openwrt.org/pipermail/openwrt-devel/2014-September/027859.html
https://lists.openwrt.org/pipermail/openwrt-devel/2014-September/027876.html
(the first one is my "favourite", a typical OpenWRT feature patch:
awesome idea, good intention, but being applied to the repo without any
peer-reviewing and broken; instead of going through upstream first...)
You'll probably want to disable the multicast-to-unicast feature
or even the bridge snooping as a whole for now.
Cheers, Linus
prev parent reply other threads:[~2014-11-16 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 12:47 [B.A.T.M.A.N.] Current OpenWrt build Jay Brussels
2014-11-12 13:54 ` Bastian Bittorf
2014-11-13 15:30 ` Jay Brussels
2014-11-15 18:58 ` Sven Eckelmann
2014-11-16 6:28 ` Linus Lüssing
2014-11-16 8:50 ` Sven Eckelmann
2014-11-16 9:14 ` Sven Eckelmann
2014-11-16 10:19 ` Linus Lüssing
2014-11-16 6:51 ` Linus Lüssing [this message]
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=20141116065123.GB2469@odroid \
--to=linus.luessing@c0d3.blue \
--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