From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"openwrt-devel@lists.openwrt.org"
<openwrt-devel@lists.openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath10k mesh + ap + encryption?
Date: Tue, 13 Sep 2016 10:59:31 +0000 [thread overview]
Message-ID: <87h99kjca5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2661831.slnB0LOeVt@prime> (Simon Wunderlich's message of "Tue, 13 Sep 2016 10:00:23 +0200")
Simon Wunderlich <sw@simonwunderlich.de> writes:
> we have done some experiments last week on ath10k, trying to run mesh=20
> (802.11s) and access point at the same time, both encrypted.=20
>
> We have tested a recent LEDE (reboot-1519-g42f559e) but with=20
> firmware-5.bin_10.2.4.70.42-2 and the included wpa_supplicant, which gave=
us a=20
> working encrypted 802.11s network. However, starting an AP at the same ti=
me=20
> didn't work (AP doesn't beacon). This wasn't a problem when 802.11s was=20
> running unencrypted.
>
> We also tested version 10.2.4.97 (from codeaurora), which is now default =
in=20
> LEDE. However, this version apparently doesn't support 11s mesh at all=20
> (WMI_SERVICE_MESH_11S is disabled in the service map, but cfg/mac80211=20
> advertises support).
>
> So here are my questions:
>
> * Did anyone succesfully run AP and mesh, both encrypted at the same tim=
e?
> * Do you have any pointers how we could fix this? Could it be fixable in=
the=20
> driver (i.e. not in firmware)?
> * Does anyone have an idea if 11s will be supported in future versions? =
I=20
> didn't find any changelogs, but having 11s mode no longer in the service =
map=20
> does not make me optimistic.
Why is LEDE using 10.2.4.97? It seems to be a quite old release and I
have no knowledge if anyone even tests that firmware branch with ath10k.
I recommend to only use firmware releases from ath10k-firmware.git as we
use those internally with ath10k. In any case, don't make any
assumptions about future from that firmware branch as it's so old.
--=20
Kalle Valo=
next prev parent reply other threads:[~2016-09-13 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 8:00 ath10k mesh + ap + encryption? Simon Wunderlich
2016-09-13 10:59 ` Valo, Kalle [this message]
2016-09-13 11:13 ` Simon Wunderlich
2016-09-13 11:25 ` Valo, Kalle
2016-09-13 11:38 ` Sebastian Gottschall
2016-09-13 12:30 ` Simon Wunderlich
2016-09-13 17:54 ` Pedersen, Thomas
2016-09-19 6:43 ` Simon Wunderlich
2016-09-19 9:34 ` [OpenWrt-Devel] " Sven Eckelmann
2017-01-24 16:41 ` Sven Eckelmann
2016-09-23 22:18 ` Pedersen, Thomas
2016-09-25 20:16 ` Simon Wunderlich
2016-09-13 18:54 ` Martin Blumenstingl
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=87h99kjca5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=sw@simonwunderlich.de \
/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;
as well as URLs for NNTP newsgroup(s).