Wireless Access

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

The kernel is currently 6.11.0, but trying slightly older kernels changed nothing. I haven't tried replacing Intel firmware because it doesn't seem to be a firmware crash or error.

Looking around there's one other mention of this message on kernel's BugZilla (https://bugzilla.kernel.org/show_bug.cgi?id=219159). The summary of that seems to be that the AP is picking an invalid channel? If I'm reading it correctly the failure condition is `!he_6ghz_oper->ccfs1`, which would mean that it fails because CCFS1 is not set properly. In any case it sounds like the very least, the kernel is stricter about non-conformant behaviour (and there are commit messages about that). 

> Management frames still use OFDM rates so disabling those will not help. 

I'd still like to try and disable all the 802.11b rates, if it's possible.

Original Message:
Sent: Apr 08, 2025 04:33 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Okay, I've also made a packet capture and the HE CCFS0 is 72, CFFS1 is 79 in the beacon frame. Primary channel is 69.

CCFS0 does look odd, shouldn't that be 71? Then 79 would be okay?

The kernel is currently 6.11.0, but trying slightly older kernels changed nothing. I haven't tried replacing Intel firmware because it doesn't seem to be a firmware crash or error.

Looking around there's one other mention of this message on kernel's BugZilla (https://bugzilla.kernel.org/show_bug.cgi?id=219159). The summary of that seems to be that the AP is picking an invalid channel? If I'm reading it correctly the failure condition is `!he_6ghz_oper->ccfs1`, which would mean that it fails because CCFS1 is not set properly. In any case it sounds like the very least, the kernel is stricter about non-conformant behaviour (and there are commit messages about that). 

> Management frames still use OFDM rates so disabling those will not help. 

I'd still like to try and disable all the 802.11b rates, if it's possible.

Original Message:
Sent: Apr 08, 2025 04:33 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

What channel width are you using in 6 GHz?

Okay, I've also made a packet capture and the HE CCFS0 is 72, CFFS1 is 79 in the beacon frame. Primary channel is 69.

CCFS0 does look odd, shouldn't that be 71? Then 79 would be okay?

The kernel is currently 6.11.0, but trying slightly older kernels changed nothing. I haven't tried replacing Intel firmware because it doesn't seem to be a firmware crash or error.

Looking around there's one other mention of this message on kernel's BugZilla (https://bugzilla.kernel.org/show_bug.cgi?id=219159). The summary of that seems to be that the AP is picking an invalid channel? If I'm reading it correctly the failure condition is `!he_6ghz_oper->ccfs1`, which would mean that it fails because CCFS1 is not set properly. In any case it sounds like the very least, the kernel is stricter about non-conformant behaviour (and there are commit messages about that). 

> Management frames still use OFDM rates so disabling those will not help. 

I'd still like to try and disable all the 802.11b rates, if it's possible.

Original Message:
Sent: Apr 08, 2025 04:33 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Okay, I've also made a packet capture and the HE CCFS0 is 72, CFFS1 is 79 in the beacon frame. Primary channel is 69.

CCFS0 does look odd, shouldn't that be 71? Then 79 would be okay?

Original Message:
Sent: Apr 09, 2025 09:23 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

The kernel is currently 6.11.0, but trying slightly older kernels changed nothing. I haven't tried replacing Intel firmware because it doesn't seem to be a firmware crash or error.

Looking around there's one other mention of this message on kernel's BugZilla (https://bugzilla.kernel.org/show_bug.cgi?id=219159). The summary of that seems to be that the AP is picking an invalid channel? If I'm reading it correctly the failure condition is `!he_6ghz_oper->ccfs1`, which would mean that it fails because CCFS1 is not set properly. In any case it sounds like the very least, the kernel is stricter about non-conformant behaviour (and there are commit messages about that). 

> Management frames still use OFDM rates so disabling those will not help. 

I'd still like to try and disable all the 802.11b rates, if it's possible.

Original Message:
Sent: Apr 08, 2025 04:33 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

I just booted up an AP-655 on 8.12.0.4 and see CCFS0 as 71 and CCFS1 as 79 which is correct based on the specification for 160 MHz at 69 in 6 GHz. What is the source showing CCFS0 as 72? Some Linux utility or is this in an OTA capture? Please verify this in OTA capture and if you see 72, please open a case and attach the pcap/tech support.

Original Message:
Sent: Apr 09, 2025 09:42 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, I've also made a packet capture and the HE CCFS0 is 72, CFFS1 is 79 in the beacon frame. Primary channel is 69.

CCFS0 does look odd, shouldn't that be 71? Then 79 would be okay?

Original Message:
Sent: Apr 09, 2025 09:23 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

The kernel is currently 6.11.0, but trying slightly older kernels changed nothing. I haven't tried replacing Intel firmware because it doesn't seem to be a firmware crash or error.

Looking around there's one other mention of this message on kernel's BugZilla (https://bugzilla.kernel.org/show_bug.cgi?id=219159). The summary of that seems to be that the AP is picking an invalid channel? If I'm reading it correctly the failure condition is `!he_6ghz_oper->ccfs1`, which would mean that it fails because CCFS1 is not set properly. In any case it sounds like the very least, the kernel is stricter about non-conformant behaviour (and there are commit messages about that). 

> Management frames still use OFDM rates so disabling those will not help. 

I'd still like to try and disable all the 802.11b rates, if it's possible.

Original Message:
Sent: Apr 08, 2025 04:33 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

The kernel is currently 6.11.0, but trying slightly older kernels changed nothing. I haven't tried replacing Intel firmware because it doesn't seem to be a firmware crash or error.

Looking around there's one other mention of this message on kernel's BugZilla (https://bugzilla.kernel.org/show_bug.cgi?id=219159). The summary of that seems to be that the AP is picking an invalid channel? If I'm reading it correctly the failure condition is `!he_6ghz_oper->ccfs1`, which would mean that it fails because CCFS1 is not set properly. In any case it sounds like the very least, the kernel is stricter about non-conformant behaviour (and there are commit messages about that). 

> Management frames still use OFDM rates so disabling those will not help. 

I'd still like to try and disable all the 802.11b rates, if it's possible.

Original Message:
Sent: Apr 08, 2025 04:33 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

802.11b (1, 2, 5.5, 11) rates only apply to 2.4 GHz which doesn't sound like what you're troubleshooting here.

Original Message:
Sent: Apr 09, 2025 09:23 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

The kernel is currently 6.11.0, but trying slightly older kernels changed nothing. I haven't tried replacing Intel firmware because it doesn't seem to be a firmware crash or error.

Looking around there's one other mention of this message on kernel's BugZilla (https://bugzilla.kernel.org/show_bug.cgi?id=219159). The summary of that seems to be that the AP is picking an invalid channel? If I'm reading it correctly the failure condition is `!he_6ghz_oper->ccfs1`, which would mean that it fails because CCFS1 is not set properly. In any case it sounds like the very least, the kernel is stricter about non-conformant behaviour (and there are commit messages about that). 

> Management frames still use OFDM rates so disabling those will not help. 

I'd still like to try and disable all the 802.11b rates, if it's possible.

Original Message:
Sent: Apr 08, 2025 04:33 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Management frames still use OFDM rates so disabling those will not help. Have you tried different firmware and Linux kernel versions for the AX210?  What ucode and kernel are you currently using?

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

You should be referring the IEEE 802.11 specification instead.

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Well, no idea who's right or wrong but there's an ongoing discussion about this issue actually: https://lore.kernel.org/linux-wireless/20251019112935.08f722e20f42.I69591428f2b9bde9df3c78c333e9b4fc264da0d9@changeid/

Original Message:
Sent: Apr 10, 2025 10:58 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Some APs, e.g., some versions of Aruba APs, have a bug where they advertise invalid 6 GHz Operation Information in their HE operation element in the association response.

Hmm, I think I indeed didn't check the association response because I can't capture that.

Though this patch also means that Aruba APs are going to be restricted to 802.11ax on 6GHz. (Unless this bug is fixed.)

+			/* The above check verifies only HE operation, and+			 * doesn't check EHT operation, thus set the mode to HE.+			 */+			return IEEE80211_CONN_MODE_HE;

Well, no idea who's right or wrong but there's an ongoing discussion about this issue actually: https://lore.kernel.org/linux-wireless/20251019112935.08f722e20f42.I69591428f2b9bde9df3c78c333e9b4fc264da0d9@changeid/

Original Message:
Sent: Apr 10, 2025 10:58 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

I will try to replicate the issue. Can you confirm the VAP and SSID configuration? Is 11r enabled?

Some APs, e.g., some versions of Aruba APs, have a bug where they advertise invalid 6 GHz Operation Information in their HE operation element in the association response.

Hmm, I think I indeed didn't check the association response because I can't capture that.

Though this patch also means that Aruba APs are going to be restricted to 802.11ax on 6GHz. (Unless this bug is fixed.)

+			/* The above check verifies only HE operation, and+			 * doesn't check EHT operation, thus set the mode to HE.+			 */+			return IEEE80211_CONN_MODE_HE;

Well, no idea who's right or wrong but there's an ongoing discussion about this issue actually: https://lore.kernel.org/linux-wireless/20251019112935.08f722e20f42.I69591428f2b9bde9df3c78c333e9b4fc264da0d9@changeid/

Original Message:
Sent: Apr 10, 2025 10:58 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

11r, k, v all three are enabled. WPA3-Personal. Advertise AP name for 6G and MBO for 6G is also enabled. Anything else that would matter in this context?

In an another linux-wireless thread Johannes Berg has now said that Aruba has supposedly fixed the issue and it will become available at some point. I also have no clue when though. It's a bit sad how long this has been broken already.

Original Message:
Sent: Oct 22, 2025 05:12 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I will try to replicate the issue. Can you confirm the VAP and SSID configuration? Is 11r enabled?

Original Message:
Sent: Oct 22, 2025 05:55 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Some APs, e.g., some versions of Aruba APs, have a bug where they advertise invalid 6 GHz Operation Information in their HE operation element in the association response.

Hmm, I think I indeed didn't check the association response because I can't capture that.

Though this patch also means that Aruba APs are going to be restricted to 802.11ax on 6GHz. (Unless this bug is fixed.)

+			/* The above check verifies only HE operation, and+			 * doesn't check EHT operation, thus set the mode to HE.+			 */+			return IEEE80211_CONN_MODE_HE;

Original Message:
Sent: Oct 21, 2025 07:11 AM
From: mchouque
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Well, no idea who's right or wrong but there's an ongoing discussion about this issue actually: https://lore.kernel.org/linux-wireless/20251019112935.08f722e20f42.I69591428f2b9bde9df3c78c333e9b4fc264da0d9@changeid/

Original Message:
Sent: Apr 10, 2025 10:58 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Did you open a TAC case back in April? Can you share the case number?

I've been unsuccessful at reproducing this on 8.12.0.4 so far. What forwarding mode is the VAP in? Can you share the wpa_supplicant config used when you saw wlp4s0: bad HE/EHT 6 GHz operation? The more details you can share the better.

Original Message:
Sent: Oct 23, 2025 06:48 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

11r, k, v all three are enabled. WPA3-Personal. Advertise AP name for 6G and MBO for 6G is also enabled. Anything else that would matter in this context?

In an another linux-wireless thread Johannes Berg has now said that Aruba has supposedly fixed the issue and it will become available at some point. I also have no clue when though. It's a bit sad how long this has been broken already.

Original Message:
Sent: Oct 22, 2025 05:12 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I will try to replicate the issue. Can you confirm the VAP and SSID configuration? Is 11r enabled?

Original Message:
Sent: Oct 22, 2025 05:55 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Some APs, e.g., some versions of Aruba APs, have a bug where they advertise invalid 6 GHz Operation Information in their HE operation element in the association response.

Hmm, I think I indeed didn't check the association response because I can't capture that.

Though this patch also means that Aruba APs are going to be restricted to 802.11ax on 6GHz. (Unless this bug is fixed.)

+			/* The above check verifies only HE operation, and+			 * doesn't check EHT operation, thus set the mode to HE.+			 */+			return IEEE80211_CONN_MODE_HE;

Original Message:
Sent: Oct 21, 2025 07:11 AM
From: mchouque
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Well, no idea who's right or wrong but there's an ongoing discussion about this issue actually: https://lore.kernel.org/linux-wireless/20251019112935.08f722e20f42.I69591428f2b9bde9df3c78c333e9b4fc264da0d9@changeid/

Original Message:
Sent: Apr 10, 2025 10:58 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

@mchouque and @Avamander I've reproduced this on an Intel BE200 (Linux 6.12 ucode 90) on 8.12.0.4 and the current latest 8.13.1.0. The issue seems to occur when the association request uses FT AKM:3 and the channel width is 160 MHz. I've raised AOS-271109 to track this for future reference.

Until this is fixed and released:

Workaround 1 is to disable FT (on client or AP). If wpa_supplicant config, remove FT-EAP from key_mgmt and only allow WPA-EAP-SHA256. For those reading and running 8.10.x, you will need both WPA-EAP and WPA-EAP-SHA256 to support multi-band SSIDs with 6 GHz.

Workaround 2 is to change AP maximum channel width to 80 MHz.

Original Message:
Sent: Oct 23, 2025 10:15 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Did you open a TAC case back in April? Can you share the case number?

I've been unsuccessful at reproducing this on 8.12.0.4 so far. What forwarding mode is the VAP in? Can you share the wpa_supplicant config used when you saw wlp4s0: bad HE/EHT 6 GHz operation? The more details you can share the better.

Original Message:
Sent: Oct 23, 2025 06:48 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

11r, k, v all three are enabled. WPA3-Personal. Advertise AP name for 6G and MBO for 6G is also enabled. Anything else that would matter in this context?

In an another linux-wireless thread Johannes Berg has now said that Aruba has supposedly fixed the issue and it will become available at some point. I also have no clue when though. It's a bit sad how long this has been broken already.

Original Message:
Sent: Oct 22, 2025 05:12 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I will try to replicate the issue. Can you confirm the VAP and SSID configuration? Is 11r enabled?

Original Message:
Sent: Oct 22, 2025 05:55 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Some APs, e.g., some versions of Aruba APs, have a bug where they advertise invalid 6 GHz Operation Information in their HE operation element in the association response.

Hmm, I think I indeed didn't check the association response because I can't capture that.

Though this patch also means that Aruba APs are going to be restricted to 802.11ax on 6GHz. (Unless this bug is fixed.)

+			/* The above check verifies only HE operation, and+			 * doesn't check EHT operation, thus set the mode to HE.+			 */+			return IEEE80211_CONN_MODE_HE;

Original Message:
Sent: Oct 21, 2025 07:11 AM
From: mchouque
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Well, no idea who's right or wrong but there's an ongoing discussion about this issue actually: https://lore.kernel.org/linux-wireless/20251019112935.08f722e20f42.I69591428f2b9bde9df3c78c333e9b4fc264da0d9@changeid/

Original Message:
Sent: Apr 10, 2025 10:58 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Problem is still present after upgrading to 8.13.1.1_94375

@mchouque and @Avamander I've reproduced this on an Intel BE200 (Linux 6.12 ucode 90) on 8.12.0.4 and the current latest 8.13.1.0. The issue seems to occur when the association request uses FT AKM:3 and the channel width is 160 MHz. I've raised AOS-271109 to track this for future reference.

Until this is fixed and released:

Workaround 1 is to disable FT (on client or AP). If wpa_supplicant config, remove FT-EAP from key_mgmt and only allow WPA-EAP-SHA256. For those reading and running 8.10.x, you will need both WPA-EAP and WPA-EAP-SHA256 to support multi-band SSIDs with 6 GHz.

Workaround 2 is to change AP maximum channel width to 80 MHz.

Original Message:
Sent: Oct 23, 2025 10:15 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Did you open a TAC case back in April? Can you share the case number?

I've been unsuccessful at reproducing this on 8.12.0.4 so far. What forwarding mode is the VAP in? Can you share the wpa_supplicant config used when you saw wlp4s0: bad HE/EHT 6 GHz operation? The more details you can share the better.

Original Message:
Sent: Oct 23, 2025 06:48 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

11r, k, v all three are enabled. WPA3-Personal. Advertise AP name for 6G and MBO for 6G is also enabled. Anything else that would matter in this context?

In an another linux-wireless thread Johannes Berg has now said that Aruba has supposedly fixed the issue and it will become available at some point. I also have no clue when though. It's a bit sad how long this has been broken already.

Original Message:
Sent: Oct 22, 2025 05:12 PM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I will try to replicate the issue. Can you confirm the VAP and SSID configuration? Is 11r enabled?

Original Message:
Sent: Oct 22, 2025 05:55 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Some APs, e.g., some versions of Aruba APs, have a bug where they advertise invalid 6 GHz Operation Information in their HE operation element in the association response.

Hmm, I think I indeed didn't check the association response because I can't capture that.

Though this patch also means that Aruba APs are going to be restricted to 802.11ax on 6GHz. (Unless this bug is fixed.)

+			/* The above check verifies only HE operation, and+			 * doesn't check EHT operation, thus set the mode to HE.+			 */+			return IEEE80211_CONN_MODE_HE;

Original Message:
Sent: Oct 21, 2025 07:11 AM
From: mchouque
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Well, no idea who's right or wrong but there's an ongoing discussion about this issue actually: https://lore.kernel.org/linux-wireless/20251019112935.08f722e20f42.I69591428f2b9bde9df3c78c333e9b4fc264da0d9@changeid/

Original Message:
Sent: Apr 10, 2025 10:58 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> You should be referring the IEEE 802.11 specification instead.

Indeed. I decided to get access to the 802.11ax-2023 specification myself, and it does indeed say that for 160MHz operation, CCFS1 must be larger than 0 and the absolute difference between CCFS0 and CCFS1 must be exactly 8. Which does indeed mean that at least this part is correct.

Thank you for saying that they were incorrect about this part.

Original Message:
Sent: Apr 10, 2025 10:38 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

You should be referring the IEEE 802.11 specification instead.

Original Message:
Sent: Apr 10, 2025 10:34 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

> The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Well, they said "Your AP seems to be sending broken information." and "You can refer to https://en.wikipedia.org/wiki/List_of_WLAN_channels to see what's valid and what is not."

Original Message:
Sent: Apr 10, 2025 08:28 AM
From: schmelzle
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

No, that's not correct.

The APs are broadcasting the correct CCFS0 (71) and CCFS1 (79) for 160 MHz at 69 in 6 GHz.

The Intel engineer needs to re-review the specification if they are actually claiming these channel indexes for CCFS0/1 are wrong.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander Salamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?

I also just checked an Intel BE200 on Linux and the Intel client connects just fine to 160 MHz at channel 69 in 6 GHz.

Original Message:
Sent: Apr 10, 2025 05:09 AM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

Okay, looking into this further. It does seem like Aruba AP-s are broadcasting an invalid CCFS1. It was confirmed by an Intel engineer on kernel's bugzilla. 

In my case if CCFS0 is 71, CCFS1 should be the next valid channel so probably 87 (71 + 80MHz). Not 79, as 79 does not seem to even be in the valid channel list.

However I don't know if I have the access to actually report this to tech support (I would appreciate if someone else tried as well). As it stands it seems like Intel cards and Linux both refuse the 6GHz operation offered by Aruba APs on 6GHz.

Original Message:
Sent: Apr 05, 2025 07:56 PM
From: Avamander
Subject: AP-655 6GHz / 6E incompatibility with Intel AX210

I've been trying to get AP-655 working with AX210 clients on the 6GHz band. Both Windows and Linux clients on Intel chipsets seem to just refuse to connect.

Linux clients seem to complain about some kind of mode change:

wlp4s0: bad HE/EHT 6 GHz operation
wlp4s0: AP appears to change mode (expected HE, found legacy), disconnect

These 6GHz SSID do however work with MacOS and they're legal to use (have been allowed for a while now). Though at a subpar performance, I have a few 802.11ac access points that achieve better latency and jitter on 5GHz, and speeds at the same bandwidth/stream count. But this performance is probably a separate issue and there are a few other threads about this. (Disappointing nevertheless.)

I can't seem to find any configuration option for disabling legacy operations (I guess anything below 802.11n?) for ArubaOS 8.12.0.4. I did try to change a/g mininum and allowed rates, but those seem to have had no effect. (I still see those legacy rates listed in iw scan output.)

Is this a known issue? Can I somehow disable a/b/g operations to try and see if this improves things?