> because sdata->u.sta.supp_rates_bits is set only when we actually > join an ibss, which is not the case in this scenario; so we assign > zero here. Then, the code in rate_control_pid_rate_init() calls > rate_lowest_index() for some reason, and since no supported rate is > found, this warning is issued. > > > The question is how sta->supp_rates should be initialized: > > - we could initialize it to our sta's rates, but then we could > probably transmit to a station at unsupported rate > > - add new ibss station only on received beacon, not on a data frame; > currently, beacons are ignored for this purpose (they just update > the bss list later on) > > - something else (like 1Mbps only)? > > As soon as we do sta_join_ibss(), this warning won't happen again. > > > Note that once we have sta entry (in our ibss), we will update its > supported rates based on beacons it sends (in rx_bss_info()). > > Any thoughts? I don't know. I don't use IBSS nor am I intimately familiar with the specs for it. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
