On Wed, Feb 23, 2022 at 01:39:33PM +0100, Arend van Spriel wrote: > On 2/23/2022 11:46 AM, Veerendranath Jakkam wrote: > > In contrast, NL80211_IFTYPE_MLO_LINK can't be used to represent AP MLO > > link since an MLD AP must support pre-11be and 11be clients > > simultaneously so each AP MLO link affiliated with AP MLD must also act > > as independent AP for pre-11be clients so each AP MLO link must be > > Not just for pre-11be clients. 11be clients can opt-out right? > > > represented by NL80211_IFTYPE_AP associated with a separate netdev. > > > > Two link AP MLD representation: > > > > AP MLD > > (netdev + wdev) > > / \ > > / \ > > wlan0 wlan1 > > IFTYPE_AP IFTYPE_AP > > (netdev + wdev) (netdev + wdev) > > | | > > | | > > radio(2G) radio(5G) > > So the AP MLD is a new IFTYPE? Earlier discussions were suggesting the AP > MLO links would be bridged, but then there would be only a netdev at AP MLD > level, right? Yes, having a separate interface type for AP MLD sound like a clean approach. Apart from the data path, AP MLD will be involved in control path as well. AP MLD has its own wdev. Some of the control path APIs using AP MLD interface are link affiliation/removal, remote MLD STA add, PTK key installation, and intra-bss forwarding configuration. Also EAPoL frames are expected on AP MLD interface. Vasanth
