From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Bjoern Franke <bjo@nord-west.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org,
freifunk-ol-dev <freifunk-ol-dev@lists.nord-west.net>
Subject: Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3
Date: Fri, 12 Jun 2015 06:32:41 +0200 [thread overview]
Message-ID: <20150612043240.GA27325@odroid> (raw)
In-Reply-To: <1434033854.25497.3.camel@nord-west.org>
On Thu, Jun 11, 2015 at 04:44:14PM +0200, Bjoern Franke wrote:
> Hi Marek,
>
>
> > Do you have the multicast optimizations enabled ? 2014.3.0 still has
> > a known
> > bug causing these optimizations to harm multicast traffic. Either
> > disable this
> > feature or upgrade to something newer than 2014.3.0.
> >
>
> IThanks for your reply. Multicast optimizations are disabled, but we ha
> ve multicast related errors in the logs:
> br-mesh: Multicast hash table chain limit reached: bat0br-mesh: Cannot rehash multicast hash table, disabling snooping: bat0, 201, -22
> Regardsbjo
There's a hash_max value for the bridge
(/sys/class/net/<br>/bridge/hash_max). By default it's rather
small, just 512 entries / multicast listeners, so it's expected that
with 500 nodes the bridge multicast snooping will shut down.
Nevertheless, even if the bridge deactivates its multicast
snooping that shouldn't cause trouble for ICMPv6.
Which firmware are you using, do you see ICMPv6 packets entering
bat0 on the gateway and leaving bat0 on the router?
Cheers, Linus
next prev parent reply other threads:[~2015-06-12 4:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 12:19 [B.A.T.M.A.N.] Mesh hickups with 2014.3 Bjoern Franke
2015-06-11 12:43 ` Hans-Werner Hilse
2015-06-12 15:20 ` Bjoern Franke
2015-06-12 20:39 ` Hans-Werner Hilse
2015-06-11 13:20 ` Marek Lindner
2015-06-11 14:44 ` Bjoern Franke
2015-06-12 2:53 ` Marek Lindner
2015-06-12 4:32 ` Linus Lüssing [this message]
[not found] ` <1434121488.3296.8.camel@nord-west.org>
2015-06-12 20:33 ` Linus Lüssing
2015-06-14 10:20 ` 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=20150612043240.GA27325@odroid \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bjo@nord-west.org \
--cc=freifunk-ol-dev@lists.nord-west.net \
/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