Proper operating class definition for class 137?
Johannes Berg
johannes at sipsolutions.net
Wed Feb 4 08:15:51 PST 2026
On Wed, 2026-02-04 at 17:00 +0100, Pablo MARTIN-GOMEZ wrote:
> > /* IEEE P802.11be/D5.0, Table E-4 (Global operating classes) */
> > - { HOSTAPD_MODE_IEEE80211A, 137, 31, 191, 32, BW320, NO_P2P_SUPP },
> > + { HOSTAPD_MODE_IEEE80211A, 137, 1, 233, 64, BW320, NO_P2P_SUPP },
>
> I'm going with: both code are incorrect but by chance both work.
>
> The "correct" change would be:
>
> - { HOSTAPD_MODE_IEEE80211A, 137, 31, 191, 32, BW320, NO_P2P_SUPP },
> + { HOSTAPD_MODE_IEEE80211A, 137, 1, 233, 32, BW320, NO_P2P_SUPP },
>
> [`32` is not the size of a channel, it's the increment to go to one
> channel to the next, one particularity of op class 137 is its channels
> overlap, so yes a channel stops at +64, but the next (overlapping)
> channel starts at +32]
Why 1/233 though? Table E-4 (as of REVmf D2.0 at least) literally says
center frequencies are channel 31, 63, 95, 127, 159, 191 which is
covered by the original definition, no?
I think maybe the change was intended for U-NII-9 but then that should
only make it 31, 223, I'd guess? But not sure how that's being handled
as far as the spec is concerned.
johannes
More information about the Hostap
mailing list