From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ob0-x22c.google.com ([2607:f8b0:4003:c01::22c]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1aMm8a-0004oo-Kj for ath10k@lists.infradead.org; Sat, 23 Jan 2016 00:33:12 +0000 Received: by mail-ob0-x22c.google.com with SMTP id is5so76389366obc.0 for ; Fri, 22 Jan 2016 16:32:46 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20160122125155.GI14453@localhost> Date: Sat, 23 Jan 2016 08:32:45 +0800 Message-ID: Subject: Re: Mesh on ath10k drops all packets From: Yeoh Chun-Yeow List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Jeroen Roovers Cc: Bob Copeland , "ath10k@lists.infradead.org" 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? ---- Chun-Yeow _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k