Release Asuswrt-Merlin 3006.102.6 is now available

[jksmurf]

One, one device only @jksmurf and it never fully connects, will review carefully as a quick read covered most of the easy /obvious stuff I did. Sent you a DM, will try a couple of ther things tomorrow and update...

Maybe it just wants to be an individual; a rebel without a cause (to connect).
You can't fault it for that...

 

[aex.perez]

Well it's fixed and broken. I had to disable both MLO and WiFi 7 on the main SSID for it to connect on the custom 2.4Ghz SSID (that never had WiFi7 or MLO).

Disabling 6Ghz in the main SSID had no effect
Limiting the 2.4Ghz SSID to one node running ASUS FW and off the router had no effect
The only thing that allowed it to connect, get an IP, and stay connected without the WLC_SCD_DEAUTHORIZE is removing MLO and WiFi 7 from the main (different from the separate/custom 2.4Ghz SSID only)

After some Google

• WLC_SCB_DEAUTHORIZE: The Wireless LAN Controller (WLC) failed to deauthorize a Station Control Block (SCB) entry.
• Error (-30): A specific error code indicating the driver couldn't manage the client's state during a disconnect.
• Broadcom Bug: The issue stems from the Broadcom kernel driver, often related to complex Wi-Fi 7 (MLO) or power-saving features

Sort of reminds of the 3004.388.9.0 relese on my old AX routers/nodes with WPA2/WPA3 being broken until 3004.388.9.2

But doing this wreaked havoc on everything else, so ultimately may just start over, and make it like a fancy AX router to get everything working again if I can fix/stabilize it

 

[jksmurf]

Well it's fixed and broken. I had to disable both MLO and WiFi 7 on the main SSID for it to connect on the custom 2.4Ghz SSID (that never had WiFi7 or MLO).

just start over, and make it like a fancy AX router to get everything working again

Well that just sucks. I’m sorry to hear that.

While I don’t read the Wi-Fi 7 forums in detail, you’re not alone it seems, there’s a growing crescendo of complaints that M,O is simply not working, which might be a good thing in the longer term, if ASUS ever sort it out properly. I’m sure they don’t test it with every combination of modern clients and older clients or devices with notoriously weak Wi-Fi.

This is why I originally thought “coaxing” it onto your specific band with Trigger, STA, roaming disabled and a fixed channel (and vertically aligned antennas…) would be worth a shot but it seems like the MLO or Wi-Fi 7 decision making logic is simply dominating the conversation, if you like; and not in a good way.

 

[aex.perez]

Well that just sucks. I’m sorry to hear that.

While I don’t read the Wi-Fi 7 forums in detail, you’re not alone it seems, there’s a growing crescendo of complaints that M,O is simply not working, which might be a good thing in the longer term, if ASUS ever sort it out properly. I’m sure they don’t test it with every combination of modern clients and older clients or devices with notoriously weak Wi-Fi.

This is why I originally thought “coaxing” it onto your specific band with Trigger, STA, roaming disabled and a fixed channel (and vertically aligned antennas…) would be worth a shot but it seems like the MLO or Wi-Fi 7 decision making logic is simply dominating the conversation, if you like; and not in a good way.

Appreciate that, but the client in question was always on the 2.4Ghz band as the SSID it was using was only enabled for the 2.4Ghz band and it roamed to the router which is nearest to it. The loog shows it connecting, and DHCP offering an IP but that's where it end. I even assigned a fixed IP in the DHCP LAN settings to no avail. Now I'll look to see if via its app I can assign it a static IP.

In case your wondering, not working with stock FW either.

 

[jksmurf]

Now I'll look to see if via its app I can assign it a static IP.

Good idea. My Shelly’s all have static IPs on the device, set by me. Whether it helps with the router vacillating over when or whether to give it an IP I’ll never really know, but it’s been solid, along with my other tweaks. But I’m on Wi-Fi 6, so MLO isn’t jumping in.

In case you’re wondering, not working with stock FW either.

Well I can’t say it’s kept me up nights, but it’s good to have that ruled out.

 

[aex.perez]

Appreciate that, but the client in question was always on the 2.4Ghz band as the SSID it was using was only enabled for the 2.4Ghz band and it roamed to the router which is nearest to it. The loog shows it connecting, and DHCP offering an IP but that's where it end. I even assigned a fixed IP in the DHCP LAN settings to no avail. Now I'll look to see if via its app I can assign it a static IP.

In case your wondering, not working with stock FW either.

UPDATE: It does work both Merlin and stock, for a time it connected in both circumstances, and its connnected now. But why?

The only thing that comes to mind, as I've been changing things. Is that I had one of the other SSIDs (Guest) with 6Ghz enabled at one point, and I just removed it and rebooted the router and it connects even with WiFi7 and MLO enabled on the main SSID

Now keeping VERY verbose and detailed notes going forward on any changes and rebooting the router between them to see if it falls off again and stays off and what the trigger might be Also going to try and join that client it to the Main SSID with WiFi7/MLO just to rule that out or in as the case may be.

Also need to check authentication method or WPA/WPA2 vs WPA2 vs WPA2/WPA3 (WPA/WP2 for the 2.4 and 5Ghz SSID andWPA2/WPA3 for the main MLO based one is what's working now)

 

[aex.perez]

UPDATE: It does work both Merlin and stock, for a time it connected in both circumstances, and its connnected now. But why?

The only thing that comes to mind, as I've been changing things. Is that I had one of the other SSIDs (Guest) with 6Ghz enabled at one point, and I just removed it and rebooted the router and it connects even with WiFi7 and MLO enabled on the main SSID

Now keeping VERY verbose and detailed notes going forward on any changes and rebooting the router between them to see if it falls off again and stays off and what the trigger might be Also going to try and join that client it to the Main SSID with WiFi7/MLO just to rule that out or in as the case may be.

Also need to check authentication method or WPA/WPA2 vs WPA2 vs WPA2/WPA3 (WPA/WP2 for the 2.4 and 5Ghz SSID andWPA2/WPA3 for the main MLO based one is what's working now)

Now I'm totally confused. The device connected to the MLO SSID and is on it solid on 2.4Ghz radio even with the other two enabled for that SSID. This wasn't working at all before
So on the weekend back to 3006.102.6 I go and we'll see if it stays on, now that everything is working, though I wish I knew why

Just tested again after looking at the wireless log, 2.4Ghz AX mode on the tablets is working as well, same MLO based SSID that also wasn't working