[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hostap
Subject:    RE: [PATCH 10/50] AP: Include an RNR element in beacons for MLD AP
From:       "Otcheretianski, Andrei" <andrei.otcheretianski () intel ! com>
Date:       2023-02-21 9:51:52
Message-ID: DM6PR11MB3897C9ED7662019FC98544D2F5A59 () DM6PR11MB3897 ! namprd11 ! prod ! outlook ! com
[Download RAW message or body]

> > @@ -6642,7 +6670,12 @@ static u8 * hostapd_eid_rnr_iface(struct
> > hostapd_data *hapd,
> >  		}
> >
> >  		tbtt_count_pos = eid++;
> > -		*eid++ = RNR_TBTT_INFO_LEN;
> > +

> For Lower band AP collocated with a 6GHz AP, RNR Element carrying ML
> Partner information should be a separate element from the one that carried
> OOB information Is it handled here ?

Both co-located and ML Bss's are reported in the same rnr ie. Why should it be a separate element?

> > +#ifdef CONFIG_IEEE80211BE
> > +				*eid++ = hapd->conf->mld_id;
> mld id is 0 if its not MBSS case i.e. If the reported AP is part of same MLD as
> reporting AP then mld id should be 0.

Correct. We have this fix internally already. I will resent this part.

Andrei


_______________________________________________
Hostap mailing list
Hostap@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/hostap
[prev in list] [next in list] [prev in thread] [next in thread]