From: Russell Senior <russell@personaltelco.net>
To: Xuebing Wang <xbing6@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org, openwrt-devel@lists.openwrt.org,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [B.A.T.M.A.N.] [OpenWrt-Devel] [ath10k] [batman-adv] Robustness of batman-adv or IBSS/802.11s on ath9k (AR9331 chip)
Date: Sat, 22 Apr 2017 01:55:07 -0700 [thread overview]
Message-ID: <87fuh095zo.fsf@husum.klickitat.com> (raw)
In-Reply-To: <52905ff0-487f-f50f-797a-6f6f1740d1d4@gmail.com> (Xuebing Wang's message of "Sat, 22 Apr 2017 13:16:11 +0800")
>>>>> "Xuebing" == Xuebing Wang <xbing6@gmail.com> writes:
Xuebing> Hi ath10k community, Does anyone use ath9k driver + 802.11s (or
Xuebing> IBSS/adhoc) on commercial products?
Xuebing> Our setup is AR9331 + ath9k driver + OpenWRT 15.05 + batman-adv
Xuebing> 2016.1 (PKG_RELEASE:=3)
Xuebing> We are very serious about robustness of running batman-adv on
Xuebing> AR9331, because we have 20+ commercial sites running, each site
Xuebing> is with about 20 nodes. - batman-adv + ar9331 work almost
Xuebing> (well almost) perfectly. - Sometimes, one node drops off the
Xuebing> mesh, occurrence rate is very low. - For one time, when Node
Xuebing> drops off the mesh, "rmmod ath9k" then "modprobe ath9k" can get
Xuebing> both batman-adv (and ibss/adhoc on top of ath9k) recover. This
Xuebing> seemingly points to that the issue is with ath9k driver
Xuebing> (ibss/adhoc mode).
I'm running batman-adv on LEDE-project (r1497) on a TP-Link TP-WDR3600
with ibss/adhoc + ap on the 2.4GHz radio. This is ath9k, not ath10k.
Seems to work fine, no problems.
--
Russell Senior, President
russell@personaltelco.net
next prev parent reply other threads:[~2017-04-22 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Russell Senior [this message]
2017-04-22 9:12 ` [B.A.T.M.A.N.] [OpenWrt-Devel] " 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=87fuh095zo.fsf@husum.klickitat.com \
--to=russell@personaltelco.net \
--cc=ath10k@lists.infradead.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=xbing6@gmail.com \
/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