On Fri, 2017-09-15 at 09:27 -0500, Denis Kenzior wrote: > > > However, you're not answering my question... > > > > Which was? > > So if we issue CMD_CONNECT with a PREV_BSSID, does/should OPERSTATE > still stay UP? It's difficult to do, but from a higher-layer POV I'd argue that it should? I'd basically argue that it's no different from 802.1X reauthentication, and the operstate docs say: -set interface back to IF_OPER_DORMANT if 802.1X reauthentication fails > > We had intended to have NL80211_CMD_ROAM to make that decision > > once, > > but never really used it for that... I think it could be > > implemented > > but I don't really know how well drivers were to support it. > > I think it would be nice. Worst case a driver won't implement it, > but we can use FT on those that do. I have no idea how you'd ask them to do FT or just normal reassoc? I guess they don't really care as long as the supplicant is in the host. johannes
