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 13:28:56 +0800	[thread overview]
Message-ID: <c9f21f91-992d-604f-91ac-4784e8258c3e@gmail.com> (raw)
In-Reply-To: <CAJ-Vmo=4-wKKV_4pXTSgVqdPOyR+zOrHbtVP4Mv9vxaueyrh=A@mail.gmail.com>

Thanks.

I did not try 40 IBSS nodes without encryption. I am using software 
encryption for ath9k because of key caching issues discussed in below 
threads:
https://patchwork.kernel.org/patch/9381651/
https://github.com/cozybit/authsae/issues/42

This is a customer site in the field, our temporary work-around is to 
create 2 networks (each is with 20 nodes) by using different SSID.

Because this is customer site in the field, it is not convenient to 
change and test. Does it make sense to test without encryption, 
encryption is a MUST?

Xuebing Wang

On 2017年06月03日 13:18, Adrian Chadd wrote:
> Hi!
>
> Does it happen if you run 40 IBSS nodes without encryption?
>
> (I wonder if it's a MAC or PHY bug..)
>
>
> -adrian
>


  reply	other threads:[~2017-06-03  5:28 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 [this message]
2017-06-03  6:16     ` Adrian Chadd
2017-06-03  6:30       ` Xuebing Wang
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=c9f21f91-992d-604f-91ac-4784e8258c3e@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