> 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. ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any retransmission, dissemination, copying or other use of, or taking of any action in reliance upon this information is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Nothing contained herein shall be deemed as a representation, warranty or a commitment by Celeno. No warranties are expressed or implied, including, but not limited to, any implied warranties of non-infringement, merchantability and fitness for a particular purpose. ________________________________ _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
