On Sun, 2022-04-17 at 14:30 +0000, Rameshkumar Sundaram (QUIC) wrote: > > > > Well, I was thinking it would reasonably come with the beacon rate, > > i.e. > > as a new attribute like NL80211_TXRATE_DUP? > Sorry not getting this, you mean hostapd would need to send new set of > rates for this configuration ? > The expectation is that user-space will set this bit in HE oper IE > only if legacy rates are present in beacon or basic rates. > ? I don't understand. The point is - you're setting the bit in the beacon that indicates "I'm transmitting it as duplicate", right? But you're also using that bit to actually configure it to do (non-HT) duplicate transmissions. But fundamentally, those two things aren't really related, are they? Why shouldn't you be - at least theoretically - be able to configure it for duplicate transmission (or not) regardless of the bit in the beacon? To me it seems "do duplicate transmission" is a property of the *rate* you want to use to transmit, not really necessarily a property of the *content* of the frame you're transmitting. johannes
