On Mon, 2013-11-11 at 12:06 -0600, Felipe Contreras wrote: > > The not receiving part is a bug. I think you're probably receiving > > beacons once associated though? > > Nope. Never. That's odd, firmware bug? But it's still odd since windows works? > Moreover, if continuing the association without beacons has a legal a > problem, that problem would exist for drivers that don't have the > IEEE80211_HW_NEED_DTIM_BEFORE_ASSOC flag, wouldn't it? How exactly > would trying to associate with need_beacon break the law, but not if > !need_beacon? Well, it's actually somewhat unlikely you'd break the law, although possible, since eventually you'd get disconnected from the AP anyway? In any case - your argumentation above isn't true because every device listens for beacons, and if none are received then it should eventually disconnect. That should be true even with your hack here. In any case, I'm not really comfortable connecting to an AP that we never ever receive beacons from. I can try to investigate why this doesn't happen on windows and what we should be doing though. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
