> > In order to not interfere with other channel activities, decrease the > > wait time to 200ms, or to 100ms in case of an active P2P GO on the > > system. > > This sounds like a risky change to do at this point in time. Why would this be > needed now more than ten years after those earlier values had been > selected and having been tested for interoperability issues over years? We got a relatively recent customer bug in a flow inviting a non-responding client with an active GO, which resulted in missing multiple beacon transmissions due to GO being too long out of its channel and eventual disconnection. I also wasn't confident about this change originally.. Would it be more acceptable to make these timeouts configurable, while keeping the original values as defaults? > > -- > Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
