From: Xuebing Wang <xbing6@gmail.com>
To: hostap@lists.infradead.org, Masashi Honma <masashi.honma@gmail.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
simon Wunderlich <sw@simonwunderlich.de>,
b.a.t.m.a.n@lists.open-mesh.org,
Jason Toschlog <jason.toschlog@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Sven Eckelmann <sven@narfation.org>
Subject: Re: [wpa_supplicant] Is there a way to limit peers (to about 12) for IBSS/adhoc?
Date: Sat, 3 Jun 2017 16:45:28 +0800 [thread overview]
Message-ID: <30a44936-a1e9-4a50-00e2-e240bb09f4a2@gmail.com> (raw)
In-Reply-To: <edc163f6-a49c-21f3-9cf1-74df6e262fdb@gmail.com>
Hi Honma-san,
Does max_peer_links apply to IBSS/adhoc (in addition to 802.11s mesh)?
Thanks.
Xuebing Wang
On 2017年06月03日 12:09, Xuebing Wang wrote:
> Hi community,
>
> This email is mainly addressed to hostap/wpa_supplicant mailing list.
>
> Descriptions of my issue:
> - I am establishing IBSS/adhoc network using OpenWRT 15.05 + ath9k
> (AR9331).
> - When nodes are relatively closely placed, the peers (the term is
> 'neighbors' in batman-adv mesh) reach 40, ath9k driver detects "tx
> hung, resetting the chip" (for RESET_TYPE_TX_HANG).
> - This ath9k "tx hung" randomly happens among the 40 nodes (in adhoc
> network), and it happens relatively often (seemingly randomly for
> nodes), and randomly makes some nodes un-usable.
> - This appears to be an issue with ath9k kernel driver or ath9k
> hardware that it can not handle ~40 peers.
> - IBSS/adhoc with 20 peers work well.
>
> Is there a config in wpa_supplicant that we can limit the number of
> peers?
>
> In the other words, once the number of peers ('iw wlan0 station dump')
> reaches a pre-configured number (e.g. 12 or 16), wpa_supplicant does
> not authenticate any more, for IBSS/adhoc only?
> - A subtle detail: once a new beacon with higher RSSI is detected, the
> current connection with lowest RSSI will be de-authenticated, and to
> authenticate this new peer (with higher RSSI in beacon).
>
> Is this "limiting number of peers for IBSS/adhoc" a good work-around
> for 40+ peers adhoc network, although the ultimate root cause
> seemingly is with ath9k kernel driver or ath9k hardware?
>
> Also, if there are many (like 40+) peers in IBSS/adhoc network, I am
> not sure how medium access contention and collisions factor in, for
> management frames?
>
> Here is my wpa_supplicant conf file:
> ------
> ctrl_interface=/var/run/wpa_supplicant
>
> # use 'ap_scan=2' on all devices connected to the network
> # this is unnecessary if you only want the network to be created when
> no other networks are available
> ap_scan=2
>
> network={
> ssid="Net-xxxxxxxx"
> mode=1
> frequency=2462
> proto=WPA2
> key_mgmt=WPA-PSK
> pairwise=CCMP
> group=CCMP
> psk="xxxxxxxx"
> }
> ------
>
> Another approach could be to use user-space shell script to "iw <dev>
> ibss leave" for the lower RSSI stations?
> - As I am using batman-adv to build mesh network on the top of
> IBSS/adhoc, a similar approach can be done at batman-adv level.
>
> Suggestions?
>
> Thanks.
> Xuebing Wang
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Xuebing Wang <xbing6@gmail.com>
To: hostap@lists.infradead.org, Masashi Honma <masashi.honma@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
b.a.t.m.a.n@lists.open-mesh.org,
simon Wunderlich <sw@simonwunderlich.de>,
Sven Eckelmann <sven@narfation.org>,
Jason Toschlog <jason.toschlog@gmail.com>,
Adrian Chadd <adrian@freebsd.org>
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 16:45:28 +0800 [thread overview]
Message-ID: <30a44936-a1e9-4a50-00e2-e240bb09f4a2@gmail.com> (raw)
In-Reply-To: <edc163f6-a49c-21f3-9cf1-74df6e262fdb@gmail.com>
Hi Honma-san,
Does max_peer_links apply to IBSS/adhoc (in addition to 802.11s mesh)?
Thanks.
Xuebing Wang
On 2017年06月03日 12:09, Xuebing Wang wrote:
> Hi community,
>
> This email is mainly addressed to hostap/wpa_supplicant mailing list.
>
> Descriptions of my issue:
> - I am establishing IBSS/adhoc network using OpenWRT 15.05 + ath9k
> (AR9331).
> - When nodes are relatively closely placed, the peers (the term is
> 'neighbors' in batman-adv mesh) reach 40, ath9k driver detects "tx
> hung, resetting the chip" (for RESET_TYPE_TX_HANG).
> - This ath9k "tx hung" randomly happens among the 40 nodes (in adhoc
> network), and it happens relatively often (seemingly randomly for
> nodes), and randomly makes some nodes un-usable.
> - This appears to be an issue with ath9k kernel driver or ath9k
> hardware that it can not handle ~40 peers.
> - IBSS/adhoc with 20 peers work well.
>
> Is there a config in wpa_supplicant that we can limit the number of
> peers?
>
> In the other words, once the number of peers ('iw wlan0 station dump')
> reaches a pre-configured number (e.g. 12 or 16), wpa_supplicant does
> not authenticate any more, for IBSS/adhoc only?
> - A subtle detail: once a new beacon with higher RSSI is detected, the
> current connection with lowest RSSI will be de-authenticated, and to
> authenticate this new peer (with higher RSSI in beacon).
>
> Is this "limiting number of peers for IBSS/adhoc" a good work-around
> for 40+ peers adhoc network, although the ultimate root cause
> seemingly is with ath9k kernel driver or ath9k hardware?
>
> Also, if there are many (like 40+) peers in IBSS/adhoc network, I am
> not sure how medium access contention and collisions factor in, for
> management frames?
>
> Here is my wpa_supplicant conf file:
> ------
> ctrl_interface=/var/run/wpa_supplicant
>
> # use 'ap_scan=2' on all devices connected to the network
> # this is unnecessary if you only want the network to be created when
> no other networks are available
> ap_scan=2
>
> network={
> ssid="Net-xxxxxxxx"
> mode=1
> frequency=2462
> proto=WPA2
> key_mgmt=WPA-PSK
> pairwise=CCMP
> group=CCMP
> psk="xxxxxxxx"
> }
> ------
>
> Another approach could be to use user-space shell script to "iw <dev>
> ibss leave" for the lower RSSI stations?
> - As I am using batman-adv to build mesh network on the top of
> IBSS/adhoc, a similar approach can be done at batman-adv level.
>
> Suggestions?
>
> Thanks.
> Xuebing Wang
>
next prev parent reply other threads:[~2017-06-03 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 4:09 [wpa_supplicant] Is there a way to limit peers (to about 12) for IBSS/adhoc? Xuebing Wang
2017-06-03 4:09 ` [B.A.T.M.A.N.] " Xuebing Wang
2017-06-03 5:18 ` Adrian Chadd
2017-06-03 5:18 ` [B.A.T.M.A.N.] " Adrian Chadd
2017-06-03 5:28 ` Xuebing Wang
2017-06-03 5:28 ` [B.A.T.M.A.N.] " Xuebing Wang
2017-06-03 6:16 ` Adrian Chadd
2017-06-03 6:16 ` [B.A.T.M.A.N.] " Adrian Chadd
2017-06-03 6:30 ` Xuebing Wang
2017-06-03 6:30 ` [B.A.T.M.A.N.] " Xuebing Wang
2017-06-03 9:21 ` Simon Wunderlich
2017-06-03 9:21 ` [B.A.T.M.A.N.] " Simon Wunderlich
2017-06-03 8:45 ` Xuebing Wang [this message]
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=30a44936-a1e9-4a50-00e2-e240bb09f4a2@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=masashi.honma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.