Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

Hi, > > Okay. In Gluon both the batman-adv multicast optimizations and > bridge multicast snooping are deactivated by default. So I think > it's probably an issue with the bridge on your gateway. Does > deactivating the batman-adv and bridge multicast stuff make a > difference? Unfortunately not

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

Hi, Am 2015-06-12 17:20, schrieb Bjoern Franke: > Public-IPv6 is announced from a gateway via radvd into the mesh. So even in that direction, NDP is fine. Seems only ICMPv6 echo requests are somewhat different then? ip -6 neigh show says "FAILED". My bad: I planned to write "RA" instead of

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

On Fri, Jun 12, 2015 at 05:04:48PM +0200, Bjoern Franke wrote: > Hi Linus, > > > There's a hash_max value for the bridge > > (/sys/class/net//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 sn

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

Hi hwh, > Continuously? So that directions seems fine then. Yep. > What does "not possible" mean? There's no reply? No reply, yes. > So it's just the gateway that can't reach the "router"? Correct. > > Public-IPv6 is announced from a gateway via radvd into the mesh. > > So even in

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

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

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

On Thursday, June 11, 2015 16:44:14 Bjoern Franke wrote: > Thanks 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: ba

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

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

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

On Thursday, June 11, 2015 14:19:23 Bjoern Franke wrote: > - ping via linklocal, ULA and public-IPv6 from gateway to router not > possible > - other routers in the same mesh can ping it via ULA etc (connected via > the same fastd-VPN) > > Public-IPv6 is announced from a gateway via radvd into the

Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3

Hi, Am 2015-06-11 14:19, schrieb Bjoern Franke: - gateway gets alfreddata from router Continuously? So that directions seems fine then. - router pingable via batctl - ping via linklocal, ULA and public-IPv6 from gateway to router not possible What does "not possible" mean? There's no repl

[B.A.T.M.A.N.] Mesh hickups with 2014.3

Hi, in the last days we upgraded nearly all (~500) routers of our Freifunk -mesh from 2013.4 to 2014.3. The most things run fine again, but with some routers we have connectivity issues as follows: - gateway gets alfreddata from router - router pingable via batctl - ping via linklocal, ULA and pu