linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Etienne Champetier <etienne.champetier@free.fr>
To: linux-wireless@vger.kernel.org, devel@lists.open80211s.org
Subject: Re: authsae, 'ath9k nohwcrypt=1' & AR9100
Date: Tue, 23 Jul 2013 23:36:49 +0200	[thread overview]
Message-ID: <51EEF771.7030102@free.fr> (raw)
In-Reply-To: <800088722.345614075.1374079656592.JavaMail.root@zimbra65-e11.priv.proxad.net>

Hi

Le 17/07/2013 18:47, etienne.champetier@free.fr a écrit :
> Hi
>
> I'm making some test with authsae on openrwt and for wr1043nd router (AR9100 wireless) i still need 'ath9k nohwcrypt=1'
> for the secure mesh to work when on another router (AR9280 wireless) i don't need it.
> Is it a drivers bug? or is it hardware?
>
> -Router A: wr1043nd (need nohwcrypt=1 option)
>   -AR9100 wireless
>   -authsae - 2013-06-25-e2f67612101dc83f2c459d8ddc75c34bc83e1e83 (https://github.com/cozybit/authsae/tree/e2f67612101dc83f2c459d8ddc75c34bc83e1e83)
>   -kmod-ath9k - 3.10.1+2013-06-27-1 (backports-20130617-4-ge3220f5)
>   -openwrt BB r37364
>
> -Router B: ubnt rspro
>   -AR9280 wireless
it's an AR9220 wireless (Mikrotik RB R52Hn), recognized as AR9280
>   -openwrt BB r37369 (same authsae/ath9k)
>
> Thanks in advance
> Etienne

This patch http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=a549459c96ba99a691aa1cafeabdd327a7a2bfcf
make AR9160 and previous (AR9100) run in promiscuous mode (in order to catch all frames), does this influence hardware encryption (hwcrypt)?

Thanks in advance
Etienne


  reply	other threads:[~2013-07-23 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <242956217.344802091.1374060921158.JavaMail.root@zimbra65-e11.priv.proxad.net>
2013-07-17 16:47 ` authsae & ath9k nohwcrypt=1 etienne.champetier
2013-07-23 21:36   ` Etienne Champetier [this message]
2013-07-25 22:56 authsae, 'ath9k nohwcrypt=1' & AR9100 Yeoh Chun-Yeow

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=51EEF771.7030102@free.fr \
    --to=etienne.champetier@free.fr \
    --cc=devel@lists.open80211s.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).