On Thu, Feb 04, 2016 at 08:27:32PM +0100, Henrik Friedrichsen wrote: > Hey, > > On Thu, Feb 04, 2016 at 06:24:42PM +0100, Stefan Sperling wrote: > > This AP does not comply with the 11n standard I'm reading (802.11 2012) > > because it does not support all of MCS 0-7. > > > > We currently require RxMCS starting with 0xff (MCS 0 to 7 supported). > > Looks like we need a better strategy to cope with the real world... > > Ow, sounds like a painful "standard" to implement. If you need any more > data or a patch tested, let me know. > > Here's another interesting tidbid: With the patches you posted I can > still associate with my WiFi AP at home (TP-Link WDR4900 running > OpenWRT), but DHCP does not work and if I set the IP statically, I > can't get to the router either. The media mode with these patches is > HT-MCS2. Reverting to the older modes (e.g. 11a) works. So this appears > to cause a regression with my setup.
Yes, that iwn driver patch has a problem. Please try -current. 11n is a moving target so if you watch for changes and keep testing that helps us a great deal. Thanks!
