From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1aMmgu-0007qG-64 for ath10k@lists.infradead.org; Sat, 23 Jan 2016 01:08:36 +0000 Message-ID: <56A2D1F6.2050307@codeaurora.org> Date: Fri, 22 Jan 2016 17:05:58 -0800 From: Peter Oh MIME-Version: 1.0 Subject: Re: Mesh on ath10k drops all packets References: <20160122125155.GI14453@localhost> In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Yeoh Chun-Yeow , Jeroen Roovers Cc: Bob Copeland , ath10k@lists.infradead.org On 01/22/2016 04:32 PM, Yeoh Chun-Yeow wrote: > On Fri, Jan 22, 2016 at 11:45 PM, Jeroen Roovers > wrote: >> On 22 January 2016 at 13:51, Bob Copeland wrote: >>> On Fri, Jan 22, 2016 at 12:01:36PM +0100, Jeroen Roovers wrote: >>>> Maybe related? >>> Could be. >> [..] >> >>> What happens with non-secure mesh, i.e.: >>> >>> user_mpm=1 >>> network={ >>> mode=5 >>> ssid="_" >>> frequency=2412 >>> key_mgmt=NONE >>> } >> That works fine! >> > 802.11ac or ath10k should only work on 5GHz, right? Mesh in ath10k works on 2.4G also. > > ---- > Chun-Yeow > > _______________________________________________ > ath10k mailing list > ath10k@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/ath10k _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k