public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6@gmail.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: hostap@lists.infradead.org,
	Jason Toschlog <jason.toschlog@gmail.com>,
	b.a.t.m.a.n@lists.open-mesh.org,
	Sven Eckelmann <sven@narfation.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [B.A.T.M.A.N.] [wpa_supplicant] Is there a way to limit peers (to about 12) for IBSS/adhoc?
Date: Sat, 3 Jun 2017 14:30:27 +0800	[thread overview]
Message-ID: <458fa88b-b6d9-d02a-8d5f-012f6c83edef@gmail.com> (raw)
In-Reply-To: <CAJ-Vmo=RnRGCEOTs6VHzTVZeex0n7OnTEiJq8jZR2cDhbnTXwA@mail.gmail.com>

Hi Adrian,

=> Is it a gradual thing?  Ie, do you know when it starts to hang? Does
it hang at 40? or gradually as you approach 40?

We do not know. What we do know is, 20 peers / neighbors work well.

Jason Toschlog in CC said that he observed similar issues with brcmfmac 
when peers reach 32 (16 peers work for him).

I guess I will setup 32 or 40 nodes here and try limit the max number of 
peers (at wpa_supplicant) for IBSS/adhoc.

Thanks again.

Xuebing Wang

On 2017年06月03日 14:16, Adrian Chadd wrote:
> Hi,
>
> Well, it sounds like something you need a 40 node test network for :)
>
> I was wondering whether it was some kind of MAC bug that was being
> triggered because of so many units say, overflowing the keycache or
> something. But if it's software encryption then maybe not. I wish I
> could help more, but setting up a 40 node network to test is a big
> challenge. :)
>
> Is it a gradual thing?  Ie, do you know when it starts to hang? Does
> it hang at 40? or gradually as you approach 40?
>
> As for association limits - I thought there was a maximum station
> parameter somewhere...
>
>
> -adrian
>


  reply	other threads:[~2017-06-03  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03  4:09 [B.A.T.M.A.N.] [wpa_supplicant] Is there a way to limit peers (to about 12) for IBSS/adhoc? Xuebing Wang
2017-06-03  5:18 ` Adrian Chadd
2017-06-03  5:28   ` Xuebing Wang
2017-06-03  6:16     ` Adrian Chadd
2017-06-03  6:30       ` Xuebing Wang [this message]
2017-06-03  9:21         ` Simon Wunderlich
2017-06-03  8:45 ` Xuebing Wang

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=458fa88b-b6d9-d02a-8d5f-012f6c83edef@gmail.com \
    --to=xbing6@gmail.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=hostap@lists.infradead.org \
    --cc=jason.toschlog@gmail.com \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    /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