From: Peter Oh <poh@codeaurora.org>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>,
Jeroen Roovers <jeroen.roovers@airfi.aero>
Cc: Bob Copeland <me@bobcopeland.com>, ath10k@lists.infradead.org
Subject: Re: Mesh on ath10k drops all packets
Date: Fri, 22 Jan 2016 17:05:58 -0800 [thread overview]
Message-ID: <56A2D1F6.2050307@codeaurora.org> (raw)
In-Reply-To: <CAEFj985BS=nOvBePEzMd-2LZAs37z=rnvBH1httesefEUsr5ZQ@mail.gmail.com>
On 01/22/2016 04:32 PM, Yeoh Chun-Yeow wrote:
> On Fri, Jan 22, 2016 at 11:45 PM, Jeroen Roovers
> <jeroen.roovers@airfi.aero> wrote:
>> On 22 January 2016 at 13:51, Bob Copeland <me@bobcopeland.com> 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
next prev parent reply other threads:[~2016-01-23 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 10:38 Mesh on ath10k drops all packets Jeroen Roovers
2016-01-22 10:55 ` Jeroen Roovers
2016-01-22 11:01 ` Jeroen Roovers
2016-01-22 12:51 ` Bob Copeland
2016-01-22 15:45 ` Jeroen Roovers
2016-01-23 0:32 ` Yeoh Chun-Yeow
2016-01-23 1:05 ` Peter Oh [this message]
2016-01-23 0:21 ` Peter Oh
2016-01-23 9:44 ` Jeroen Roovers
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=56A2D1F6.2050307@codeaurora.org \
--to=poh@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=jeroen.roovers@airfi.aero \
--cc=me@bobcopeland.com \
--cc=yeohchunyeow@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