On Mon, Sep 13, 2010 at 10:09:59AM +0900, Bruno Randolf wrote:
> i don't know wether we can encrypt management frames in HW, so until this is
> sorted out, i disabled it.
I don't think any of the hardware supported by ath5k would be able to do
this. IEEE 802.11w design changes in CCMP for managem
On Sun September 12 2010 02:22:50 m...@bobcopeland.com wrote:
> On Wed, Sep 08, 2010 at 04:04:43PM +0900, Bruno Randolf wrote:
> > Use common ath key management functions in ath5k. This fixes problems
> > with HW encryption in AP mode, which was broken in the ath5k
> > implementation.
>
> We went
On Wed, Sep 08, 2010 at 04:04:43PM +0900, Bruno Randolf wrote:
> Use common ath key management functions in ath5k. This fixes problems with HW
> encryption in AP mode, which was broken in the ath5k implementation.
We went from this:
> - key->flags |= (IEEE80211_KEY_FLAG_GENERATE_IV |
Use common ath key management functions in ath5k. This fixes problems with HW
encryption in AP mode, which was broken in the ath5k implementation.
Before (with the ath5k implementation) only one client could connect to the AP
using HW encryption and WPA. When a second client connected, the first c
