I have tried on Beryl AX and Marble but every time I flash any of the version 25 vanilla openwrt, IOT devices go haywire, going slow, laggy, delays, alexa cannot drop in on other alexas, bulbs turn off within 30 seconds if I am lucky or they never turn on or off. If I downgrade to the soon to be end of life version 24, everything works smooth and perfect. What is going on? Marble only has version 25 available, I cannot even find a version 24 for that.
FYI. I copy & paste your post into AI and it give me some hints about the situations:
It’s incredibly frustrating when a "stable" upgrade turns your smart home into a haunted house. You aren't imagining things; there is a known technical rift between the version 24 (OpenWrt 23.05/24.10 branch) and the version 25 (OpenWrt 25.12/Master branch) releases, specifically affecting MediaTek Filogic (Beryl AX) and Qualcomm (Marble) chipsets.
Here is the breakdown of why version 25 is breaking your IoT ecosystem and why Marble is stuck in this limbo.
1. The "Filogic" Latency Bug (Beryl AX)
The Beryl AX uses the MediaTek MT7981 chipset. In the version 25 branch of OpenWrt, there is a widely reported regression in the mt76 wireless driver.
The Symptom: High "jitter" and airtime unfairness. While high-bandwidth tasks (like Netflix) might seem okay, low-bandwidth, latency-sensitive pulses (like an Alexa "Drop-in" request or a light bulb heartbeat) get queued behind other traffic or dropped entirely.
Why it works on v24: Version 24 uses a more mature, stable backport of the MediaTek drivers. Version 25 often experiments with newer "upstream" kernel drivers that haven't been optimized for the specific power-management or timing requirements of cheap IoT chips (ESP8266/ESP32) found in bulbs.
2. DNS & mDNS Fragmentation
IoT devices like Alexa and smart bulbs rely heavily on mDNS (Multicast DNS) to "see" each other on the network.
In OpenWrt 25, there have been shifts in how dnsmasq and multicast traffic are handled by the firewall and bridge.
If Multicast Snooping is enabled by default (common in newer builds to save battery on mobile devices), it can accidentally "silence" your bulbs. The router thinks no one is listening to the multicast traffic and stops forwarding the "Turn on" command.
3. The "Marble" Problem (GL-B3000)
The reason you can't find a version 24 for the Marble is its chipset architecture (Qualcomm IPQ5018).
Late Bloom: The Marble is a newer device in the OpenWrt ecosystem. Official support for its specific Wi-Fi radio (ath11k/ath12k) only matured enough to be included in the "mainline" around the time version 25 development started.
The Trap: Because it’s a newer target, developers didn't bother backporting it to the older, stable v24 branch. You are essentially using "bleeding edge" drivers because they are the only drivers that exist for that hardware in the vanilla OpenWrt world.
How to Fix This (Without Downgrading)
If you are forced to stay on version 25 (especially on the Marble), try these three specific "de-optimization" steps that often fix IoT instability:
Disable 802.11ax (Wi-Fi 6) on the 2.4GHz Band:
Many older IoT bulbs cannot handle the preamble of a Wi-Fi 6 signal, even if it's supposed to be backward compatible. Force the 2.4GHz radio to 802.11n (Wi-Fi 4) mode only.
Turn Off "WMM No Acknowledgement":
In the Wireless settings (Advanced), ensure WMM is on, but "No Ack" is off. IoT devices have tiny antennas and need the router to retry if a packet isn't acknowledged.
Disable Multicast Snooping:
Go to Network -> Interfaces -> Devices. Edit your br-lan device. Under "Bridge options," find Multicast snooping and set it to off. This ensures Alexa’s "Drop-in" discovery packets actually reach the other Echo units.
The Verdict: If you value your sanity, stick to the "soon to be EOL" version 24 for the Beryl AX. In the router world, "End of Life" often just means "it actually works and we've stopped breaking it with updates." For the Marble, you may need to wait for the version 25.12.x "Service Pack" releases to stabilize the drivers.
For support for OpenWrt vanilla you should go to OpenWrt forums.
There can be many things why it isn't working, OpenWrt can become very complex with all the options and even newer options.
Some of the intended behaviour may be not that intended such as with interface creation that the default gateway checkbox is checked, whilst this checkbox basically tells that the default route must be via this interface.... which normally is expected to be wan, lan however is the only exception due to it has a special status also because it serves as designated master for ipv6.
Or that they recently decided to generate the default DUID, this however caused tons of problems for isps which do not follow this exact requirement, it is advised to delete this field inside luci -> network -> Global network options to avoid getting on a time out by the isp, only if router is used as isp router, it will likely timeout one time but after 30 minutes it should be fine again.
And yes as of the ai awnser here above, multicast snooping is not a really good idea.
Because it can terminate multicast streams so that weaker stream get more priority, usually there is only one stack and therefor snooping will do more harm than when this option is disabled.
Also it is possible there where a few regressions, which in the latest releases where present, but since I follow master directly it is already fixed there, likely you have to downgrade one more release.
3 Likes
25.12.3 was released this morning also with several CVE/Security fixes TLS fix and WiFi specific fixes among the new devices supported and fixes for numerous specific devices
1 Like
For this specific issue that has resolved this! 
Though my Marble is on a go slow with it. wolf mesh set up with vxlan to get the vlans all over same way I have my Flint 2 and Beryl AX but the Marble is dog slow 50 Mbps on 5ghz signal with 5ghz backhaul. Beryl AX gives me about 200 Mbit or more, as does Flint 2. Very strange. But it’s an improvement. I unplugged the Marble again. Maybe the next version will solve that issue.
1 Like