From: Ben Greear <greearb@candelatech.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: Simon Wunderlich <simon@open-mesh.com>,
sven@open-mesh.com, marek@open-mesh.com,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: IBSS support in ath10k - our test results and questions
Date: Tue, 07 Apr 2015 14:17:13 -0700 [thread overview]
Message-ID: <55244959.6080408@candelatech.com> (raw)
In-Reply-To: <CALhHN=qch721dGPWWjmBb15qwH8gGQprafUEK+XjYu0ajm-tZw@mail.gmail.com>
On 03/19/2015 11:44 PM, Janusz Dziedzic wrote:
> On 19 March 2015 at 22:40, Ben Greear <greearb@candelatech.com> wrote:
> Regarding IBSS/RSN and 636 firmware, this works sometimes (ath10k
> patch required here).
> But in case this don't work firmware don't send EAPOL frames - I think
> this is main problem ...
I've been trying to figure out IBSS + RSN in my firmware.
It seems in my FW I was never (or at least rarely) sending the EAPOL
frames. I found a way around this, but now I see 1/4 go out fine,
but 2/4 reports MIC errors. I don't think my work-around is to blame,
but it could be. Also not sure why my work-around is required (or at least
why STA/AP mode works w/out the hack.)
A big part of my problem is that I don't actually know how IBSS + RSN
is supposed to work.
If someone has time to clue me in on that, I might make faster progress
(or progress at all) on supporting IBSS + RSN on ath10k.
In particular, I am curious when what type of key is supposed to
be set at which stages...and for instance, what is supposed to happen
between the 1/4 message and the 2/4 message (are keys supposed to be set?)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-04-07 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:06 IBSS support in ath10k - our test results and questions Simon Wunderlich
2015-03-19 21:40 ` Ben Greear
2015-03-20 6:44 ` Janusz Dziedzic
2015-03-20 13:56 ` Ben Greear
2015-04-07 21:17 ` Ben Greear [this message]
2015-03-20 14:26 ` Simon Wunderlich
2015-03-20 15:32 ` Ben Greear
2015-03-23 11:24 ` Sven Eckelmann
2015-04-06 17:55 ` Ben Greear
2015-04-06 20:04 ` Ben Greear
2015-04-08 18:38 ` Ben Greear
2015-04-10 2:38 ` 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=55244959.6080408@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=janusz.dziedzic@tieto.com \
--cc=marek@open-mesh.com \
--cc=simon@open-mesh.com \
--cc=sven@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