From: Sven Eckelmann <sven.eckelmann@open-mesh.com>
To: openwrt-devel@lists.openwrt.org
Cc: Simon Wunderlich <sw@simonwunderlich.de>,
ath10k@lists.infradead.org, "Pedersen,
Thomas" <twp@qca.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Valo, Kalle" <kvalo@qca.qualcomm.com>
Subject: Re: [OpenWrt-Devel] ath10k mesh + ap + encryption?
Date: Mon, 19 Sep 2016 11:34:00 +0200 [thread overview]
Message-ID: <2962659.7QzjSqzP6C@bentobox> (raw)
In-Reply-To: <5898628.mmcCycDigQ@prime>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On Montag, 19. September 2016 08:43:56 CEST Simon Wunderlich wrote:
[...]
> > We're testing encrypted AP + Mesh quite successfully right now with
> > this firmware: https://github.com/kvalo/ath10k-firmware/commit/307cb46b
> > 06661ebd3186723b5002de769c7add83, of course that is for a QCA4019 chip.
> > Which chip are you using? I can poke the firmware guys for possibility
> > of getting a 10.4.3.2 firmware build for it.
>
> Hi Thomas,
>
> thanks for the hint! We are using an older QCA9882. I assume your firmware
> will not work for this one? If you can poke the firmware guys, that would
> be great.
> :)
>
> We also want to test the 70.52 firmware version next, maybe there were some
> changes since the .42 we used.
I have just checked it with 10.2.4.70.54:
| 802.11s encrypted | 802.11s unencrypted
---------------+-------------------+--------------------
AP encrypted | AP doesn't beacon | works
AP unencrypted | AP doesn't beacon | works
I've also checked 10.2.4.70.12-2 (doesn't seem to support encrypted mesh at
all) and with rawmode=1 (makes no difference).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-19 9:34 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
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 ` Sven Eckelmann [this message]
2017-01-24 16:41 ` [OpenWrt-Devel] " 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=2962659.7QzjSqzP6C@bentobox \
--to=sven.eckelmann@open-mesh.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=sw@simonwunderlich.de \
--cc=twp@qca.qualcomm.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