All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
	ath10k <ath10k@lists.infradead.org>
Subject: Getting bad MIC when trying ath10k + ath9k IBSS with RSN
Date: Tue, 07 Apr 2015 17:05:27 -0700	[thread overview]
Message-ID: <552470C7.9040002@candelatech.com> (raw)

I have been hacking on ath10k driver and firmware in attempt to enable IBSS + RSN.

Currently, I see message 1/4 in both directions, but the ath9k wpa_supplicant always reports 2/4
from ath10k station as having bad MIC (and AC supplicant dumps core shortly after when there is an EAPOL timeout,
I haven't looked into the core yet, but unlikely to be directly related to bad MIC I think since
ath9k <-> ath9k works fine).

Almost certainly this is some bug in ath10k and/or the firmware, but if someone
has some suggestions as to what it might be or how to debug it further, I would
appreciate the help!

Network capture and supplicant logs are found here:

https://www.candelatech.com/downloads/tmp/

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

             reply	other threads:[~2015-04-08  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08  0:05 Ben Greear [this message]
     [not found] ` <5524F0E9.9030208@green-communications.fr>
     [not found]   ` <55254106.7040807@candelatech.com>
     [not found]     ` <5525B8F3.4050702@candelatech.com>
2015-04-09  8:41       ` Getting bad MIC when trying ath10k + ath9k IBSS with RSN Nicolas Cavallari
2015-04-09 21:47         ` 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=552470C7.9040002@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=hostap@lists.shmoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.