public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] [ath10k] [batman-adv] Robustness of batman-adv or IBSS/802.11s on ath9k (AR9331 chip)
@ 2017-04-22  5:16 Xuebing Wang
  2017-04-22  8:55 ` [B.A.T.M.A.N.] [OpenWrt-Devel] " Russell Senior
  0 siblings, 1 reply; 3+ messages in thread
From: Xuebing Wang @ 2017-04-22  5:16 UTC (permalink / raw)
  To: ath10k@lists.infradead.org; +Cc: b.a.t.m.a.n, openwrt-devel

Hi ath10k community,

Does anyone use ath9k driver + 802.11s (or IBSS/adhoc) on commercial 
products?

Our setup is AR9331 + ath9k driver + OpenWRT 15.05 + batman-adv 2016.1 
(PKG_RELEASE:=3)

We are very serious about robustness of running batman-adv on AR9331, 
because we have 20+ commercial sites running, each site is with about 20 
nodes.
- batman-adv + ar9331 work almost (well almost) perfectly.
- Sometimes, one node drops off the mesh, occurrence rate is very low.
- For one time, when Node drops off the mesh, "rmmod ath9k" then 
"modprobe ath9k" can get both batman-adv (and ibss/adhoc on top of 
ath9k) recover. This seemingly points to that the issue is with ath9k 
driver (ibss/adhoc mode).

As this email is mainly addressed to ath10k community (rather than 
batman-adv or openwrt), does anyone commercially use 802.11s (or 
ibss/adhoc)+ ath9k/ath10k? Does 802.11s (or ibss/adhoc) + ath9k/ath10k 
work perfectly?

Thanks.
Xuebing Wang


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-04-22  9:12 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-04-22  5:16 [B.A.T.M.A.N.] [ath10k] [batman-adv] Robustness of batman-adv or IBSS/802.11s on ath9k (AR9331 chip) Xuebing Wang
2017-04-22  8:55 ` [B.A.T.M.A.N.] [OpenWrt-Devel] " Russell Senior
2017-04-22  9:12   ` Xuebing Wang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox