Hi Le 17/07/2013 18:47, etienne.champetier@xxxxxxx 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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
