On 2015-03-13 14:33, Benjamin Berg wrote:
Right now there is a bug where beaconing might not be enabled correctly
if the user has configuring multiple VIFs.
The issue surfaces if the userspace first creates the AP devices and
only then configures the first VIF (ath9k_bss_info_changed is
On Fr, 2015-03-13 at 15:27 +0100, Felix Fietkau wrote:
I sent the following patch yesterday - I think it addresses the exact
same issue. Please test it to see if it works for you as well.
The patch looks a lot better. I just backported it and it is working
just fine for me.
Benjamin
Benjamin Berg benja...@sipsolutions.net writes:
Right now there is a bug where beaconing might not be enabled correctly
if the user has configuring multiple VIFs.
The issue surfaces if the userspace first creates the AP devices and
only then configures the first VIF (ath9k_bss_info_changed is
Right now there is a bug where beaconing might not be enabled correctly
if the user has configuring multiple VIFs.
The issue surfaces if the userspace first creates the AP devices and
only then configures the first VIF (ath9k_bss_info_changed is called).
In this case the current
Any idea how far back this needs to be backported for stable?
Just to 4.0?
Thanks,
Ben
On 03/13/2015 07:27 AM, Felix Fietkau wrote:
On 2015-03-13 14:33, Benjamin Berg wrote:
Right now there is a bug where beaconing might not be enabled correctly
if the user has configuring multiple VIFs.
