Re: [PATCH 6/6] bss coloring: handle the collision and CAC events coming from the kernel

On 18.06.20 11:46, Shay Bar wrote:
>> In the current setup hostapd creates the beacons, probe responses, the
>> IEs within and does the handling. Only TIM is done in the kernel as it
>> requires state which is not present inside hostapd. I am aware that many
>> closed source vendors put their whole supplicant into the kernel, yet
>> this is not how the current opensource design works, which is to do it
>> in the userspace, thus being able to share the functionality across
>> several wifi stacks and operating systems.
>>      John
> I see.
> How about making hostapd use a random color in case he_bss_color=64
> in the .conf file ?
> Thank you for the discussion.
>
> Shay.

I was thinking the same. we can have 3 cases

* no he_bss_color - disable feature

* he_bss_color=<0..63> - default value

* he_bss_color>=63 - use os_random()

     John


_______________________________________________
Hostap mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/hostap