From: Sven Eckelmann <sven@open-mesh.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
simon@open-mesh.com, Marek Lindner <marek@open-mesh.com>
Subject: Re: CT ath10k firmware now supports IBSS + RSN
Date: Tue, 18 Aug 2015 11:38:33 +0200 [thread overview]
Message-ID: <4035168.MK6Xi4n7uL@bentobox> (raw)
In-Reply-To: <55D1FEB2.4060205@candelatech.com>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
On Monday 17 August 2015 08:33:06 Ben Greear wrote:
[...]
> > * IBSS/RSN isn't working between ath10k<->ath10k, ath9k<->ath10k
> > (works well between ath9k<->ath9k)
> > - the ath10k device doesn't seem to send its broadcast frames
> > after the handshake finished (ath9k already tries to transmit
> > bcast frames)
> > - also doesn't work with firmware-2-ct-non-commercial-full-14.bin
> > and nohwcrypt=1
>
> I believe I had ath10k to ath9k + RSN work, but I did see problems with ath10k-ath10k + RSN.
Yes, this was what I was reading in a different mail and also the reason
why I've tried to get it working for ath9k<->ath10k. But unfortunately,
I had no success.
I have also tried to use your config without the overrides and with
overrides without any success.
> I think sometimes it worked a bit, and then stopped. Truth is, my customers
> interested in IBSS are not doing encryption on the IBSS interface, so I have no plans to work on this
> soon. And, even if offered the opportunity, I'm not sure what I could do to
> improve the problem. Possibly someone at QCA would have ideas and might share
> them with me...
>
>
> > * IBSS stops working everytime an AP interface is added to the same
> > PHY (it isn't importing whether it is using WPA/WPA2 or configured
> > as open AP)
> > - tested again with ath9k on the same OpenWrt version and it
> > working quite well with 1x IBSS + 2x AP
>
> One of my customers is using AP + IBSS interface with no obvious problems
> related to concurrency. But, maybe they are doing things in a different
> order. Does it work for you if you bring up AP first and then add IBSS?
>
> This is likely fixable.
I had to hack a little bit of OpenWrt away but it seems that it works for
a simple setup to first create the adhoc interface and then sometimes later
add the AP interface.
[...]
Thanks for your feedback.
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:[~2015-08-18 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 23:32 CT ath10k firmware now supports IBSS + RSN Ben Greear
2015-04-13 17:41 ` Ben Greear
2015-04-14 0:10 ` Ben Greear
2015-04-14 5:34 ` Michal Kazior
2015-04-14 15:01 ` Ben Greear
2015-04-15 21:51 ` Ben Greear
2015-08-17 13:11 ` Sven Eckelmann
2015-08-17 15:33 ` Ben Greear
2015-08-18 9:38 ` Sven Eckelmann [this message]
2015-08-18 16:11 ` Ben Greear
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=4035168.MK6Xi4n7uL@bentobox \
--to=sven@open-mesh.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marek@open-mesh.com \
--cc=simon@open-mesh.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