# MM8108: AP expects Client to probe on another band

**URL:** <https://community.morsemicro.com/t/mm8108-ap-expects-client-to-probe-on-another-band/2080>\
**Category:** Software\
**Created:** [October 9, 2026, 2:59am UTC](https://community.morsemicro.com/t/mm8108-ap-expects-client-to-probe-on-another-band/2080 "2026-10-09T02:59:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thraen](https://avatars.discourse-cdn.com/v4/letter/t/ccd318/32.png) [@Thraen](https://community.morsemicro.com/u/Thraen)\
**Post date:** [October 9, 2026, 2:59am UTC](https://community.morsemicro.com/t/mm8108-ap-expects-client-to-probe-on-another-band/2080/1 "2026-10-09T02:59:18Z")

</div>

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](https://docs.morsemicro.com/application-notes/appnote-24-linux-porting-guide#id-7-bring-up)  
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!

---

<div class="post-metadata">

**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\
**Post date:** [October 9, 2026, 9:10pm UTC](https://community.morsemicro.com/t/mm8108-ap-expects-client-to-probe-on-another-band/2080/2 "2026-10-09T21:10:57Z")

</div>

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](https://morsemicro.github.io/mm-iot-sdk/framework/doc/html/BCF_REGDOM_SUPPORT.html)

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.

---

<div class="post-metadata">

**Author:** ![Thraen](https://avatars.discourse-cdn.com/v4/letter/t/ccd318/32.png) [@Thraen](https://community.morsemicro.com/u/Thraen)\
**Post date:** [October 13, 2026, 8:57am UTC](https://community.morsemicro.com/t/mm8108-ap-expects-client-to-probe-on-another-band/2080/3 "2026-10-13T08:57:47Z")

</div>

Hi @ajudge !

Thanks for your response.  
I use those versions:  
wpa\_supplicant v2.12-morse\_micro-rel\_1\_17\_9\_2026\_Apr\_20  
hostapd v2.12-morse\_micro-rel\_1\_17\_9\_2026\_Apr\_20

Can i use this `channelization_scheme` in both config files?

Thanks in advance!