On Tue, 2012-09-04 at 18:55 +0200, Christian Lamparter wrote: > > By the way, current secured mesh requires the AES CMAC to be enabled. > > But without enabling IEEE80211_HW_MFP_CAPABLE, the key cannot be added > > since this cipher suite is considered not supported. But actually AES > > CMAC can be done in software. Any work around on this? > > > I think you can override this by supplying your own custom set > of available ciphers. This is done by setting > hw.wiphy->cipher_suites > hw.wiphy->n_cipher_suites > during the initalization of the driver (i.e.: before > ieee80211_register_hw(hw) is called).
Yes, that's the way you could do it, but my argument that it's pointless still stands, so what good would it do? johannes _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
