From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Russell Senior References: <52905ff0-487f-f50f-797a-6f6f1740d1d4@gmail.com> Date: Sat, 22 Apr 2017 01:55:07 -0700 In-Reply-To: <52905ff0-487f-f50f-797a-6f6f1740d1d4@gmail.com> (Xuebing Wang's message of "Sat, 22 Apr 2017 13:16:11 +0800") Message-ID: <87fuh095zo.fsf@husum.klickitat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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) List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xuebing Wang Cc: b.a.t.m.a.n@lists.open-mesh.org, openwrt-devel@lists.openwrt.org, "ath10k@lists.infradead.org" >>>>> "Xuebing" == Xuebing Wang 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