[PATCH] WNM: Fallback to full scan when BTM contains incorrect channel info

Benjamin Berg benjamin at sipsolutions.net
Fri Oct 10 07:55:07 PDT 2025


Hi,

it would be good if you put the patch into the mail directly rather
than attaching it. Other than that, you should also adjust the
indentation for the nei->freq parameter.


Do you have an example of an RNR with incorrect information (and maybe
information of where the AP is actually)?

>From a logic perspective, this does not seem quite right to me. We do
not want to trigger a full scan, just because we are unable to e.g. use
the 6 GHz band in our station.

Though I do see now that there is a small bug and we should move the

  has_6ghz |= is_6ghz_freq(nei->freq);

assignment into the same chan_supported check. I'll submit a patch for
that.

Depending on what the AP reports in the RNR, maybe we could address
your problem by adding a check that the specified frequency is a valid
channel using e.g. ieee80211_freq_to_chan?

Benjamin

On Thu, 2025-10-09 at 17:21 -0700, Ashish Shukla wrote:
> 
> _______________________________________________
> Hostap mailing list
> Hostap at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/hostap



More information about the Hostap mailing list