Hi,
Recently, with a new vendor update, we're seeing neighbor reports being
sent out that are incompatible when referenced against the beacons. The
3rd byte of the country code in the beacon is 0x04 (table E-4) while the
neighbor report is using operating classes from a regional table e.g.
values like 1, 2 or 3.
This is entirely on the vendor as they either need to change their
hostapd config (not set "country3=0x04") or change their SET_NEIGHBOR
command to use global operating classes. But it got me wondering if
there was anything hostapd could do to guard against this. I checked
SET_NEIGHBOR and it does no validation on the neighbor report bytes. Is
this something hostapd would be willing to accept if it was committed?
or is it intended to use the neighbor report as-is, without any validation?
Thanks,
James
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
