MM8108: AP expects Client to probe on another band

Software
1

Hi,

I feel I am really close to have my two dongles connect to each other, but I get the following message on the AP when I use wpa_supplicant on the client:
Probe request not on primary: -1 != -2

It seems that’s the AP sees the Client requests, but rejects them because of this.

I used the recommended configurations from there: APPNOTE-24 Linux Porting Guide | Application notes | Morse Micro documentation
I just had to switch the following parameters in hostapd:
op_class=49
channel=55
country_code=AU

I feel something is wrong with my configuration, but none of my tests worked.

Thanks in advance for your help!

2

Hey @Thraen

What version are you using on both the AP and Client side? Not sure I’ve seen this error before but being the AU region I can speculate it has something to do with channelisation. See our mm-iot-sdk docs for the different AU channelisation - Morse Micro IoT SDK: BCF regulatory channel support

There is a new module parameter channelization_scheme for the dot11ah module which let’s you select from AU-2020 (1) to AU-REVMF (3) where the latter is the new proposed channelisation for AU from IEEE.

Make sure both AP and client agree on channelisation in AU reg domains.

I’ll raise a request to get various public facing documentation updated here, especially if this ends up being your issue.