On Fri, 2019-02-22 at 21:50 +0100, Alexander Wetzel wrote: > > No, but if you have a good test case we can check out what the firmware > > bug is and fix it. Perhaps not for all, but for the future at least. > > Maybe we can still figure out where it was introduced and thus see where > > it's good to use native mode. > > I'll verify if can reproduce the scrambled packets and will provide a > capture if so. Assuming that confirms the initial finding I'll be able > to reproduce that at will within minutes with access to a test system > having a mvm card. (I have some plans which will improve access, but > looks like that will take some time and efforts.) > > For now I handle that as low prio till we have generic Extended Key ID > support merged
Agree > and I've had some time to improve my test setup and > hopefully have better access to a mvm card for testing. If all that's lacking is a few NICs then I'm sure we/I can help out with that :) > > > I also have tested patch for iwldvm using the Compat mode and I think > > > mvm cards will also work with that. > > > > No they don't, no firmware is available for that. > > So far I only looked at the dvm part of iwlwifi with only minutes spend > on mvm to port the NATIVE solution from dvm. :) > Are you saying that mvm cards can't seamless switch a RX/TX key to TX > only one? mvm seems to support SW crypto as needed and switching RX/TX > to TX keys is the only other requirement for COMPAT mode. No, sorry. I misread your statement. I thought you were saying "mvm cards will also work with iwldvm" rather than "mvm cards will also work with compat mode" :-) I think they all should just be made to work in native mode, the firmware basically supports this as you found, there must be some small bugs. johannes
