2011/1/15 Steve Brown <sbrown@xxxxxxxxxxxx>: > On Sat, 2011-01-15 at 00:19 +0100, Björn Smedman wrote: >> This is another comment that is a little out of place but when I see >> the identifier beacon_interval in this context I cannot help bringing >> up per-vif settings as a related problem: If I read the code (or >> rather the lack of code) correctly the beacon interval of the last (or >> first?) beaconing vif added will be used to set up beacon tx, whereas >> the actual beacon contents will reflect the beacon intervals >> configured for individual vifs which may all be different... The same >> goes for e.g. tx queue configuration, no? [snip] > For instance, an ap vif has a ~100ms interval and a mesh vif has a > ~1000ms interval. I don't see how to avoid a per vif interval. I agree. We should fix ath9k so it works correctly even if beacon interval is different for different vifs (within some reasonable limits). In the mean time, as a workaround, try to configure the same beacon interval for all vifs. /Björn -- 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
