Hi, > > It just doesn't seem useful to print the message - there's nothing you > > can do about it, it basically means we ignore it and keep transmitting > > with a lower NSS (which is fine anyway, it's subject to rate control and > > the AP cannot have any expectation on how many streams we really use), > > and so it's not actionable to the user in any way. > > In some cases, people can contact the router manufacturer asking to look > into their firmware. Yeah, maybe? But like I said, it also shouldn't have much consequences - it's perhaps saying "I now can receive up to 8 streams" but only supports 4, so that's physically impossible. Maybe we could allow 4 in that case, but right now we're careful and just ignore that instruction. And in most cases the client only will have two anyway. Not that I know the numbers for your case :) > > but it's easy to tell what that value is from the association and/or > > beacon, so it didn't really seem all that useful. Perhaps more to be > > said for simply disconnecting in this case in strict mode, or > > something, so it's noticeable to people working on this/testing it. > Maybe. I have never heard of strict mode. ;-) You probably wouldn't want to use it :) but we want to behave more strictly when we're testing with APs etc. before they ship to customers, we can get these kinds of issues fixed. > For the ignorant like me, > having more details in the log message would help, as it’s not so easy > for me to capture and interpret the beacon. ;-) Well, if we made each of these messages tell a story about how to figure out what could be wrong, that'd probably be too verbose ;-) You can see the values with just $ iw wlan0 scan dump and looking for your AP's data. You'd have to understand that too, but honestly just knowing say "8 > 4" doesn't really help much either, you still have to understand where the 4 comes from and that requires looking at the details like that. Anyway ... I'll just put in this patch I think :) johannes
