Recent content by sdts

That's good info to have. Do you mind me asking what type of device the Mac address(es) in your errors match up to?

Known problem. Usually with Google devices or Sonos. You're not alone https://www.snbforums.com/threads/ax86u-filled-with-error-failed-status-37-wsize-64-policy-1.70289/ https://www.snbforums.com/threads/in-some-dire-need-of-assistance-ax86u.67944/page-5#post-669083 Raised a ticket with ASUS...

They occur when you have google home devices on your network and highlight the bug that ASUS has in their .386 code line over and above their .384 code line where this never occured and google home devices didn't have an issue. Possibly also affects SONOS devices. You'll notice the mac address...

This is the essence of it. 384 has no issues with Google home minis or Sonos. 386 is broken for them. No setting is going to fix that and as Merlin mentioned, the wifi code is closed source, so it's going to be the same regardless of whether stock firmware or merlinwrt. Doesnt sound like...

Can confirm .384 firmware fixes the problem (along with connection problems for google and sonos devices).

Same issue on the 386 firmware. Frustrating welcome to asus wifi routers ¯\_(ツ)_/¯ Good to have the easy feedback tab though. Anyone know if fixed in the beta firmware with the dnsmasq CVE fixes? Guessing not as it looked like a special release just for the CVE's? Will try eventually, but...