public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] ICMP6 flood or nodes limit ?
Date: Sun, 29 Jul 2018 23:38:53 +0800	[thread overview]
Message-ID: <1833430.pAuEAP8rMv@rousseau> (raw)
In-Reply-To: <CALb7xhz53Z+ykBxAGgEb5oixf-KVHXTc_ooECZ2ZMARxDvvnfg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]

On Thursday, 26 July 2018 14:14:14 HKT Nicu Pavel wrote:
> I'm also not sure about the originators list, if you look at the
> attached file, all originators TQ is pretty low and also each
> originator has all other hosts as NextHop. Not sure if this is correct
> or can affect.
> All these 30 hosts are pretty close to one another.

It might be (as Linus has suggested) related to poor connectivity / airtime 
overcrowding. Though for that to be the case, I'd expect a more gradual packet 
loss symptoms - not a complete collapse when you switch from 31 to 32 devices.


> > If you check the mailing list archives you will see the wifi driver issue
> > coming up on a regular basis. This example discussion is merely a few days
> > old:
> > 
> > https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2018-July/017952.html
> 
> Yes, I found that thread, but problem is quite different as with
> RealTek chipsets seems like nothing really works.

My point was rather to consider that the WiFi driver has its fingers in the 
pot too. It is somewhat unlikely that your issues are exactly the same as 
mentioned in this randomly selected thread. 

By the way, searching for 'brcmfmac adhoc' returns quite a number of hits 
mentioning complaints concerning Rasberry PIs. Have you tried running your 
setup without enabling batman-adv at all ? Since all of the devices are so 
close to each other batman-adv is not needed. Pure adhoc mode will work just 
fine. This test will help you figuring out whether the ICMPv6 misbehavior is 
related to batman-adv or not.

Cheers,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-07-29 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 19:50 [B.A.T.M.A.N.] ICMP6 flood or nodes limit ? Nicu Pavel
2018-07-26  1:12 ` Marek Lindner
2018-07-26  6:14   ` Nicu Pavel
2018-07-29 15:38     ` Marek Lindner [this message]
2018-07-26  7:24 ` Linus Lüssing

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=1833430.pAuEAP8rMv@rousseau \
    --to=mareklindner@neomailbox.ch \
    --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