# ECSA Extended Channel Switch Announcement — deterministic failure pattern by 5G-mapped UNII band (rel\_1\_17\_8\_2026\_Mar\_24)

**URL:** <https://community.morsemicro.com/t/ecsa-extended-channel-switch-announcement-deterministic-failure-pattern-by-5g-mapped-unii-band-rel-1-17-8-2026-mar-24/1743>\
**Category:** General\
**Created:** [June 14, 2026, 8:16am UTC](https://community.morsemicro.com/t/ecsa-extended-channel-switch-announcement-deterministic-failure-pattern-by-5g-mapped-unii-band-rel-1-17-8-2026-mar-24/1743 "2026-06-14T08:16:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Asaftv](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@Asaftv](https://community.morsemicro.com/u/Asaftv)\
**Post date:** [June 14, 2026, 8:16am UTC](https://community.morsemicro.com/t/ecsa-extended-channel-switch-announcement-deterministic-failure-pattern-by-5g-mapped-unii-band-rel-1-17-8-2026-mar-24/1743/1 "2026-06-14T08:16:20Z")

</div>

Hi Morse team,

Following up on:

> [@ECSA - Extended Channel Switch Announcement is not working](https://community.morsemicro.com/t/ecsa-extended-channel-switch-announcement-is-not-working/217):
>
> I am currently using the Morse Micro MM6108 HaLow in mesh mode. I am searching for a tool that can modify the channel and bandwidth through CSA (wireless beacons). We came across the ecsa\_info command with the ‘morsectrl/morse\_clil’ utility, which is intended to change the channel and bandwidth via the CSA beacon. However, when I tried using the ecsa\_info command, it did not change the channel and bandwidth as expected. ‘ecsa\_info’ help, morsectrl -i morse1 ecsa\_info --help ecsa\_info…

We applied ajudge’s recommended `chan_switch` syntax (kHz freqs,  
prim\_bandwidth, sec\_channel\_offset, no op\_class) and the AP-side IE  
is now correctly populated (op\_bw, prim\_bw, vht, ht all non-zero).  
After running a 4-step matrix of channel switches in a row on  
identical hardware, we found that the STA-side mac80211 behaviour  
is NOT intermittent — it’s DETERMINISTIC, depending on which  
5 GHz-mapped UNII band the destination falls into:

- Destination mapped into UNII-2C (5500-5720 MHz) — STA follows  
the in-band CSA seamlessly, no disconnect, kernel logs  
CTRL-EVENT-CHANNEL-SWITCH / morse: post\_channel\_switch
- Destination mapped into UNII-3 (5745-5825 MHz) — STA mac80211  
rejects with “switches to unsupported channel … width:5”  
and disconnects, full reassoc needed (~28 s downtime)

The dependent variable is the destination’s regdom permissibility  
under the cfg80211 compat shim — UNII-3 at 160 MHz width is  
restricted by US regdom, UNII-2C at 160 MHz is allowed under DFS.  
Full reproduction + logs below.

== Hardware / firmware (both AP and STA) ==

Hardware: MM8108 EKH01 module  
Build: rel\_1\_17\_8\_2026\_Mar\_24

- hostapd\_s1g rel\_1\_17\_8\_2026\_Mar\_24-1
- wpa\_supplicant\_s1g rel\_1\_17\_8\_2026\_Mar\_24-1
- kmod-morse 5.15.189+rel\_1\_17\_8\_2026\_Mar\_24-1
- morse-fw-8108 rel\_1\_17\_8\_2026\_Mar\_24-1
- morsectrl rel\_1\_17\_8\_2026\_Mar\_24-1
- morse-regdb v2.7.0-1
- wpad-openssl 2023-09-08-e5ccbfc6-8
- kernel 5.15.189, iw 5.19  
Regulatory: country=US, 8 MHz HaLow operation

AP runs hostapd\_s1g with FT-SAE enabled per the OpenWrt FT wiki  
(ieee80211r=1, mobility\_domain=a1b2, ft\_psk\_generate\_local=0,  
nas\_identifier=, r1\_key\_holder=,  
reassociation\_deadline=20000, sae\_pwe=0, ieee80211k=1).  
Full hostapd-phy0-wlan0.conf in Appendix A.

STA associates with `key_mgmt=FT-SAE` and we observe `auth_alg=ft`  
on reassoc events — FT itself works fine.

== Test matrix (4 chan\_switch invocations, in order, on the same  
running pair; CSA-OOB workaround DISABLED throughout) ==

Test 1: 8 MHz CH\_28 → 8 MHz CH\_44  
Test 2: 8 MHz CH\_44 → 2 MHz @ 923 MHz (your community example)  
Test 3: 2 MHz @ 923 MHz → 8 MHz CH\_28  
Test 4: 8 MHz CH\_28 → 8 MHz CH\_44 (repeat of test 1)

== Test 1 — 8 MHz CH\_28 → 8 MHz CH\_44 ==

AP command:  
$ hostapd\_cli\_s1g -i wlan0 chan\_switch 10 920500  
prim\_bandwidth=1 sec\_channel\_offset=1  
center\_freq1=924000 bandwidth=8  
OK

AP hostapd log:  
hostapd\_s1g: wlan0: IEEE 802.11 CHAN\_SWITCH EHT config 0x2  
HE config 0x2 VHT config 0x1  
hostapd\_s1g: hostapd\_fill\_csa\_settings : ECSA info op\_bw=160,  
prim\_bw=1, vht=1, ht=1, change to oldconfig:  
ht=1, vht=1

AP `iw dev wlan0 info` post-switch:  
channel 149 (5745 MHz), width: 160 MHz, center1: 5815 MHz

STA kernel + supplicant log:  
[4414.171472] wlan0: AP 0c:bf:74:00:1f:05 switches to  
unsupported channel (5745.000 MHz, width:5,  
CF1/2: 5815.000/0 MHz), disconnecting  
wpa\_supplicant\_s1g: wlan0: CTRL-EVENT-DISCONNECTED  
bssid=0c:bf:74:00:1f:05 reason=4 locally\_generated=1  
wpa\_supplicant\_s1g: wlan0: Added BSSID 0c:bf:74:00:1f:05 into  
ignore list, ignoring for 10 seconds

STA recovery: full reassoc ~28 s later.  
Result: FAILED — width:5 = NL80211\_CHAN\_WIDTH\_160; 5745 MHz center +  
160 MHz width is not in the US 5 GHz regdom permission set  
for non-DFS use → mac80211 rejects.

== Test 2 — 8 MHz CH\_44 → 2 MHz @ 923 MHz (your community example) ==

AP command:  
$ hostapd\_cli\_s1g -i wlan0 chan\_switch 10 922500  
prim\_bandwidth=1 sec\_channel\_offset=1  
center\_freq1=923000 bandwidth=2  
OK

AP `iw dev wlan0 info` post-switch:  
channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz

STA log: NO new lines from kernel/wpa\_supplicant\_s1g.  
STA `iw dev wlan0 link` post-switch (no disconnect ever happened):  
Connected to 0c:bf:74:00:1f:05 (on wlan0)  
SSID: g7-AP-00000001  
freq: 5785  
RX: 49318 bytes (353 packets) [traffic flowing]  
STA `wpa_cli status`: wpa\_state=COMPLETED, key\_mgmt=FT-SAE,  
freq=5785

Result: ZERO-HANDOFF SUCCESS — STA followed the in-band CSA  
seamlessly. width:40 = NL80211\_CHAN\_WIDTH\_40, permitted  
freely under US regdom.

== Test 3 — 2 MHz @ 923 MHz → 8 MHz CH\_28 ==

AP command:  
$ hostapd\_cli\_s1g -i wlan0 chan\_switch 10 912500  
prim\_bandwidth=1 sec\_channel\_offset=1  
center\_freq1=916000 bandwidth=8  
OK

AP `iw dev wlan0 info` post-switch:  
channel 100 (5500 MHz), width: 160 MHz, center1: 5570 MHz

STA log (verbatim, demonstrates clean CSA-follow):  
[5598.120591] morse: pre\_channel\_switch: count=4,  
target\_freq=5500 MHz, blockTX=0  
wpa\_supplicant\_s1g: wlan0: CTRL-EVENT-STARTED-CHANNEL-SWITCH  
freq=5500 ht\_enabled=1 ch\_offset=1  
ch\_width=160 MHz cf1=5570 cf2=0  
wpa\_supplicant\_s1g: wlan0: CTRL-EVENT-CHANNEL-SWITCH freq=5500  
ht\_enabled=1 ch\_offset=1 ch\_width=160 MHz  
cf1=5570 cf2=0  
[5598.837043] morse: post\_channel\_switch — countdown reached 0,  
finalizing

STA `wpa_cli status` post-switch: wpa\_state=COMPLETED,  
key\_mgmt=FT-SAE, freq=5500  
STA `iw dev wlan0 link`: Connected, traffic flowing on freq 5500.

Result: SUCCESS — STA followed the in-band CSA at 160 MHz width.  
The kernel-level CSA-follow path WORKS when destination is  
mapped into a US-regdom-permitted band.

== Test 4 — 8 MHz CH\_28 → 8 MHz CH\_44 (repeat of test 1) ==

Same AP command as test 1. AP moved to channel 149 / 5745 MHz /  
width 160 successfully.  
STA disconnected and reassociated after ~28 s — same outcome as  
test 1. NOT intermittent — fully reproducible.

== The deterministic pattern ==

Same chan\_switch API, same supplicant, same hardware, same  
rel\_1\_17\_8\_2026\_Mar\_24 build. The difference is purely the  
destination’s cfg80211-mapped UNII band:

Destination cfg80211-mapped Result

* * *

HaLow CH\_28 5500 MHz / 160 MHz / UNII-2C FOLLOW ✓  
HaLow CH\_44 5745 MHz / 160 MHz / UNII-3 REJECT ✗  
2 MHz @ 923 MHz 5785 MHz / 40 MHz FOLLOW ✓

Under US regdom, 160 MHz emission is permitted in UNII-2C  
(5500-5720) under DFS rules and forbidden in UNII-3 (5745-5825).  
The cfg80211 compat shim that presents the 8 MHz S1G block as a  
5 GHz 160 MHz channel inherits this regdom check at the  
destination side, even though the S1G regdom (which is what  
actually applies on the radio) does permit the move.

== Questions ==

1. Is this deterministic destination-band-dependent rejection a  
known issue on rel\_1\_17\_8\_2026\_Mar\_24? Has it been addressed  
in a newer build?

2. Can the cfg80211 compat shim be patched to bypass the 5 GHz  
regdom check during a CSA follow when the original PHY is  
S1G (i.e. let the S1G regdom govern)? Or alternatively, can  
the mapping for HaLow CH\_44 avoid landing on a UNII-3 freq?

3. Is there a runtime override (morsectrl flag, kernel  
parameter, or wpa\_supplicant\_s1g option) that we can set  
on the STA side to disable the 5 GHz regdom check for these  
mapped channels?

4. If the user-space workaround is the only option for now,  
can you confirm which HaLow channels in US are SAFE to use  
for in-band CSA without hitting this issue? Our reading of  
the US plan is anything mapped under UNII-2C is safe; CH\_44  
mapped into UNII-3 is not.

5. Are there any other UNII bands besides UNII-3 that will  
trigger the same rejection (UNII-1 / UNII-4)?

A 60-second sniffer pcap + full kernel logread for any of the  
above tests is available on request. The snippets are the load-  
bearing lines.

Thanks,

───── APPENDIX A: AP hostapd-phy0-wlan0.conf (passphrases redacted) ─────

driver=nl80211  
logger\_syslog=127  
logger\_syslog\_level=2  
logger\_stdout=127  
logger\_stdout\_level=2  
country\_code=US  
hw\_mode=a  
channel=28  
chanlist=28  
op\_class=4  
s1g\_capab=[SHORT-GI-ALL]  
s1g\_prim\_chwidth=1  
s1g\_prim\_1mhz\_chan\_index=3

ieee80211ah=1  
anti\_clogging\_threshold=99999

interface=wlan0  
ctrl\_interface=/var/run/hostapd\_s1g  
ap\_isolate=1  
bss\_load\_update\_period=60  
chan\_util\_avg\_period=600  
disassoc\_low\_ack=0  
skip\_inactivity\_poll=0  
preamble=1  
wmm\_enabled=1  
ignore\_broadcast\_ssid=0  
uapsd\_advertisement\_enabled=1  
utf8\_ssid=1  
multi\_ap=0  
beacon\_int=100  
wpa\_group\_rekey=604800  
nas\_identifier=0cbf74001f05  
sae\_require\_mfp=1  
wpa\_passphrase=  
sae\_password=  
wpa\_psk\_file=/var/run/hostapd-wlan0.psk  
auth\_algs=1  
wpa=2  
wpa\_pairwise=CCMP  
ssid=g7-AP-00000001  
bridge=br-lan  
wds\_bridge=  
wnm\_sleep\_mode=1  
bss\_transition=1  
rrm\_neighbor\_report=1  
rrm\_beacon\_report=1  
mobility\_domain=a1b2  
ft\_psk\_generate\_local=0  
ft\_over\_ds=0  
reassociation\_deadline=20000  
r1\_key\_holder=0cbf74001f05  
r0\_key\_lifetime=10000  
pmk\_r1\_push=0  
r0kh=ff:ff:ff:ff:ff:ff \* 80ab93aff49137476a8acededb853f3a  
r1kh=00:00:00:00:00:00 00:00:00:00:00:00 80ab93aff49137476a8acededb853f3a  
wpa\_disable\_eapol\_key\_retries=0  
wpa\_key\_mgmt=SAE FT-SAE  
okc=1  
ieee80211w=2  
group\_mgmt\_cipher=AES-128-CMAC  
wds\_sta=1  
bssid=0c:bf:74:00:1f:05  
sae\_pwe=0  
dpp\_configurator\_connectivity=1  
raw=0

(TX queue / WMM blocks at defaults — omitted)

───── APPENDIX B: STA full kernel + supplicant log (Test 1, failing) ─────

(captured with CSA-OOB workaround DISABLED so only the in-band CSA  
path is exercised; kernel uptime stamps in [seconds])

[4390.369166] kern.info wlan0: deauthenticating from  
0c:bf:74:00:1f:05 by local choice  
(Reason: 2=PREV\_AUTH\_NOT\_VALID)  
daemon.notice wpa\_supplicant\_s1g: wlan0:  
SME: Deauth request to the driver failed  
[4414.171472] kern.info wlan0: AP 0c:bf:74:00:1f:05 switches to  
unsupported channel (5745.000 MHz, width:5,  
CF1/2: 5815.000/0 MHz), disconnecting  
daemon.notice wpa\_supplicant\_s1g: wlan0:  
CTRL-EVENT-DISCONNECTED bssid=0c:bf:74:00:1f:05  
reason=4 locally\_generated=1  
daemon.notice wpa\_supplicant\_s1g: wlan0: Added BSSID  
0c:bf:74:00:1f:05 into ignore list, ignoring  
for 10 seconds

───── APPENDIX C: STA full kernel + supplicant log (Test 3, succeeding) ─────

(same CSA-OOB-disabled setup; switching back into UNII-2C-mapped  
destination — CSA follow works at the kernel level)

[5598.120591] kern.info morse: pre\_channel\_switch: count=4,  
target\_freq=5500 MHz, blockTX=0  
daemon.notice wpa\_supplicant\_s1g: wlan0:  
CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5500  
ht\_enabled=1 ch\_offset=1 ch\_width=160 MHz  
cf1=5570 cf2=0  
daemon.notice wpa\_supplicant\_s1g: wlan0:  
CTRL-EVENT-CHANNEL-SWITCH freq=5500  
ht\_enabled=1 ch\_offset=1 ch\_width=160 MHz  
cf1=5570 cf2=0  
[5598.837043] kern.info morse: post\_channel\_switch — countdown  
reached 0, finalizing

No disconnect, no reassoc. STA stays on the same BSS, traffic  
continues, wpa\_state remains COMPLETED, key\_mgmt remains FT-SAE.

───── APPENDIX D: AP hostapd log (chan\_switch path, all tests) ─────

daemon.info hostapd\_s1g: wlan0: IEEE 802.11 CHAN\_SWITCH EHT config 0x2  
HE config 0x2 VHT config 0x1  
daemon.notice hostapd\_s1g: hostapd\_fill\_csa\_settings : ECSA info  
op\_bw=160, prim\_bw=1, vht=1, ht=1,  
change to oldconfig: ht=1, vht=1

(ECSA IE correctly populated for all 4 tests; the AP-side API works  
as documented in your community thread regardless of destination.)

---

<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:** [June 18, 2026, 3:55am UTC](https://community.morsemicro.com/t/ecsa-extended-channel-switch-announcement-deterministic-failure-pattern-by-5g-mapped-unii-band-rel-1-17-8-2026-mar-24/1743/2 "2026-06-18T03:55:30Z")

</div>

Hi @Asaftv

Your thread is very difficult to read. Taking the time to apply some better formatting to your post will help us follow your data and questions and get you a solution faster. In many cases, I will help users format their posts correctly but this is quite verbose. Please take the time to format it.

* * *

> [@Asaftv](#):
>
> The cfg80211 compat shim that presents the 8 MHz S1G block as a  
> 5 GHz 160 MHz channel inherits this regdom check at the  
> destination side, even though the S1G regdom (which is what  
> actually applies on the radio) does permit the move.

I am very skeptical of this comment. We register to the Linux kernel as a self-managed regdom, and are not behest to the standard 5GHz regulatory limits. Have a look at the output of `iw reg get` and you will find that this range is valid, and we do not inherit the same regdom checks. Something else is happening here.

> [@Asaftv](#):
>
> 1. Is this deterministic destination-band-dependent rejection a  
> known issue on rel\_1\_17\_8\_2026\_Mar\_24? Has it been addressed  
> in a newer build?

The current CSA implementation will not allow you to switch to the same primary channel. From the logs you have provided that is not happening here.

> [@Asaftv](#):
>
> A 60-second sniffer pcap + full kernel logread for any of the  
> above tests is available on request. The snippets are the load-  
> bearing lines.

Please provide the sniffer pcap on the destination channel and the original channel.

> [@Asaftv](#):
>
> ───── APPENDIX B: STA full kernel + supplicant log (Test 1, failing) ─────
> 
> (captured with CSA-OOB workaround DISABLED so only the in-band CSA  
> path is exercised; kernel uptime stamps in [seconds])
> 
> [4390.369166] kern.info wlan0: deauthenticating from  
> 0c:bf:74:00:1f:05 by local choice  
> (Reason: 2=PREV\_AUTH\_NOT\_VALID)  
> daemon.notice wpa\_supplicant\_s1g: wlan0:  
> SME: Deauth request to the driver failed  
> [4414.171472] kern.info wlan0: AP 0c:bf:74:00:1f:05 switches to  
> unsupported channel (5745.000 MHz, width:5,  
> CF1/2: 5815.000/0 MHz), disconnecting  
> daemon.notice wpa\_supplicant\_s1g: wlan0:  
> CTRL-EVENT-DISCONNECTED bssid=0c:bf:74:00:1f:05  
> reason=4 locally\_generated=1  
> daemon.notice wpa\_supplicant\_s1g: wlan0: Added BSSID  
> 0c:bf:74:00:1f:05 into ignore list, ignoring  
> for 10 seconds

The data in this log is interesting. Your station as deauthenticated prior to or during the channel switch. Why? Are you able to increase supplicant log verbosity prior to the channel switch.

* * *

Are you able to reproduce the errors outside of a system configured for 802.11r. Does the channel switch fail using a single AP (No 802.11r enabled) + Station and SAE auth.

---

<div class="post-metadata">

**Author:** ![Asaftv](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@Asaftv](https://community.morsemicro.com/u/Asaftv)\
**Post date:** [June 26, 2026, 5:30am UTC](https://community.morsemicro.com/t/ecsa-extended-channel-switch-announcement-deterministic-failure-pattern-by-5g-mapped-unii-band-rel-1-17-8-2026-mar-24/1743/3 "2026-06-26T05:30:37Z")

</div>

Hi,

Thanks — you’re right, let me separate cleanly.

# REPEATER (this thread)

The multi-VIF AP+STA bring-up that started this thread is largely  
resolved with the guidance you gave us:

• STA-first orchestration (associate the STA backhaul first,  
then enable the downlink AP).  
• morse.ko loaded with enable\_ps=0, enable\_dynamic\_ps\_offload=0,  
enable\_pre\_assoc\_ps=0 — eliminates the  
`morse_cmd_set_ps [vif:1] failed -19` cascade.  
• sae\_pwe=2 on both wpa\_supplicant\_s1g and hostapd\_s1g sides  
(HALOWLINK2 interop).

The REPEATER now comes up reliably and stays associated.  
Considering this thread resolved — thank you for the help.

# CSA-specific issue

The STA-side ECSA non-follow is a separate, narrower issue and  
I’m moving the discussion to #1743 as you suggested. Short  
context for whoever reads this later: with a plain STA on EKH01  
associated to a HALOWLINK2 AP, `hostapd_cli_s1g chan_switch`  
on the AP causes the STA to disconnect rather than follow the  
announcement, even though the AP emits a valid ECSA IE  
(op\_bw=160, prim\_bw=2). Logs and reproducer attached to the  
#1743 thread.

# Best, Asaf

ATTACHMENTS (6)

Scenario A (LuCI/UCI channel change — your “not a CSA” path):  
mm\_dumps\_203\_REPEATER\_channel-change.tar.gz ← STA side  
mm\_dumps\_202\_AP\_channel-change.tar.gz ← AP side

Scenario B (real CSA via hostapd\_cli\_s1g chan\_switch):  
mm\_dumps\_203\_REPEATER\_csa-test.tar.gz ← STA side (didn’t follow)  
mm\_dumps\_202\_AP\_csa-test.tar.gz ← AP side (emitted ECSA)

Baselines:  
mm\_dumps\_203\_REPEATER\_2026-06-19.tar.gz ← REPEATER baseline  
mm\_dumps\_201\_AP\_2026-06-19.tar.gz ← second AP for context

Thanks,  
Asaf

[mm\_dumps\_203\_REPEATER\_csa-test.tar.gz](https://community.morsemicro.com/uploads/short-url/aYY3qU073udnOH33URTULSnAk8G.gz) (1.4 MB)

[mm\_dumps\_203\_REPEATER\_channel-change.tar.gz](https://community.morsemicro.com/uploads/short-url/bLdQudklx1LcGYRUS5oIWEVNYEW.gz) (1.4 MB)

[mm\_dumps\_203\_REPEATER\_2026-06-19.tar.gz](https://community.morsemicro.com/uploads/short-url/cFvkb9wRqBeeamPBVMg3JJcQ9sS.gz) (1.4 MB)

[mm\_dumps\_202\_AP\_csa-test.tar.gz](https://community.morsemicro.com/uploads/short-url/9w4gFC2uaWMTqzmc7YptnRLbIFr.gz) (289.7 KB)

[mm\_dumps\_202\_AP\_channel-change.tar.gz](https://community.morsemicro.com/uploads/short-url/uL9AVCFPlxHFe5KiNqpXIn94yZz.gz) (293.2 KB)

[mm\_dumps\_202\_AP\_2026-06-19.tar.gz](https://community.morsemicro.com/uploads/short-url/8gpzsEYvmSEk87ZRzHeOAiTIlxC.gz) (297.5 KB)

[mm\_dumps\_201\_AP\_2026-06-19.tar.gz](https://community.morsemicro.com/uploads/short-url/g3shCKSepMdRHFsJQ1HgrsTkOq6.gz) (1.4 MB)

---

<div class="post-metadata">

**Author:** ![Asaftv](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@Asaftv](https://community.morsemicro.com/u/Asaftv)\
**Post date:** [July 17, 2026, 8:15am UTC](https://community.morsemicro.com/t/ecsa-extended-channel-switch-announcement-deterministic-failure-pattern-by-5g-mapped-unii-band-rel-1-17-8-2026-mar-24/1743/4 "2026-07-17T08:15:35Z")

</div>

## **Baseline (both AP and STA are UCM)**

| | **value** |
| --- | --- |
| Chip / transport | MM8108 over **USB** (`lsusb 325b:8100`) |
| Kernel | **6.6.63** (i.MX8MP, Compulab) |
| morse.ko / fw / hostapd\_s1g / wpa\_supplicant\_s1g | `rel_1_17_8_2026_Mar_24` |
| OpenWrt | 24.10-SNAPSHOT |
| Regulatory | country=US, self-managed regdom |
| `iw reg get` 160 MHz ranges | `(5170-5330 @ 160)`, `(5490-5650 @ 160)`, `(5735-5895 @ 160)` — all three present |

## **What we measured (live, 100 ms link sampling on the STA)**

Command form (per your #217 guidance, kHz freqs, no op\_class): `hostapd_cli_s1g -i wlan0 chan_switch 10 <freq_kHz> prim_bandwidth=<b> sec_channel_offset=1 center_freq1=<c_kHz> bandwidth=<BW>`

| **BW** | **mapped width** | **result on UCM (6.6.63/USB)** |
| --- | --- | --- |
| **2 MHz** | 40 MHz | ✅ **reliable seamless across ALL bands** — e.g. CH\_42 (UNII-3, 5785) → CH\_6 (UNII-1, 5190): `STARTED-CHANNEL-SWITCH` → `CHANNEL-SWITCH` both fire, **0/300 samples down** |
| **4 MHz** | 80 MHz | ❌ to UNII-3 (CH\_40, 5775): STA gets `STARTED` then `DISCONNECTED reason=4`; **AP wedges `s1g_freq=-1`** |
| **8 MHz** | 160 MHz | ⚠ **unreliable** — CH\_28→CH\_12 completed once; CH\_12→CH\_28 got `STARTED` then `DISCONNECTED reason=4` ~5 s later; **CH\_44 (5815) wedges `s1g_freq=-1`** (only `wifi down; wifi up` recovers) |

## **The key cross-platform contrast**

The **same 8 MHz / 160 MHz switch** that **completes cleanly on EKH01** (kernel 5.15 / SDIO):

```auto
# EKH01 STA (5.15/SDIO) — CH_12, 160 MHz — CLEAN:
CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5180 ch_width=160 MHz cf1=5250
CTRL-EVENT-CHANNEL-SWITCH freq=5180 ch_width=160 MHz cf1=5250 <-- completes

```

is **unreliable on UCM** (kernel 6.6.63 / USB) — the STA logs `STARTED` but often never the completing `CHANNEL-SWITCH`; instead:

```auto
# UCM STA (6.6.63/USB) — CH_12->CH_28, 160 MHz — FAILS:
CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5500 ch_width=160 MHz cf1=5570
CTRL-EVENT-DISCONNECTED bssid=… reason=4 locally_generated=1 <-- ~5 s later, no completion

```

and for CH\_44 the **AP** side wedges (`hostapd_cli_s1g status` → `s1g_freq=-1`, “AP is in CSA process, reject auth” on associating STAs).

## **Questions**

1. Is in-band ECSA at **8 MHz (160 MHz-mapped)** expected to be reliable on the **USB / kernel-6.6.63** MM8108 build, or is SDIO / 5.15 the only validated path? The completion is deterministic-clean on 5.15/SDIO and marginal on 6.6.63/USB with identical userspace.
2. Why does **2 MHz (40 MHz-mapped)** follow reliably across all bands while **8 MHz (160 MHz-mapped)** does not, given all three 160 MHz ranges are present in the self-managed `iw reg get`? (You noted in #1743 you are _not_ behest to 5 GHz regdom limits — so what gates the 160 MHz completion?)
3. The AP-side **`s1g_freq=-1` wedge** on a failed 8 MHz switch requires a full `wifi down; wifi up` — `wifi reload` does not clear it. Is hostapd/ driver state cleanup on a rejected ECSA a known gap on this build?
4. Is there a driver/firmware build (e.g. 1.17.9+) that addresses the 6.6.63/USB CSA-completion path, or a recommended `cs_count` / parameter set for 8 MHz over USB?

Full 60 s pcaps (AP + STA, both the working 2 MHz case and the failing 8 MHz case) available on request.
