Recent content by RMerlin

Software issues, and they are getting resolved.

No. Each router model has its own model-specific components, you cannot substitude components from a different model.

Just to confirm it, try configuring a 5 GHz Guest Network (make sure LAN access is still allowed, if your ShieldTV is accessing a local file server), and connect your Shield to it.

JS error fixed on the Wireless Pro page (bad GPL merge), thank you for reporting it. EDIT: uploaded a new test build with the fixed page.

The GPL archive is different because it contains precompiled binary blobs for the proprietary bits and has all the confidential source files removed, while the firmware release is built directly from the full source code. So, it's normal for them to differ. Basically the workflow goes like...

Roaming and Connect to Low Powered Channels are both disabled here.

It's probably on default settings since I usually connect my Shield with an Ethernet cable. I just unplugged it, and connected to the BE92U wifi to test it. The Shield is definitely on the 5 GHz band since I use different SSIDs per band.

1) Javascript error, I'll look into it. 2) I also own a Shield TV 2019. I just connected it without any problem to the 5 GHz band. It's currently playing a 3+ hours Youtube stream. Make sure your Shield Experience is up-to-date, and double check your settings. 3) Feels just the same to me.

I just uploaded a 3006.102.7_1 test build for the RT-BE92U, based off GPL 102_39848. I have been unable to reproduce the CPU crashes / clock rollback issues with that new build. Please give this build a try. http://www.asuswrt-merlin.net/test-builds

Try just restarting that radio before resetting everything else. Webui level issues wouldn't surprise me due to the recent changes. I already provided a number of fixes to Asus over the past few months.

Behaviour of 102.6 and 102.7 is identical (no change in GPL for that model with 102.7). The last change was with 102.6. So if it worked correctly with 102.6, something else might be responsible - try just disabling and re-enabling the 2.4 GHz radio to restart it.

First quick tests are looking good with the new RT-BE92U GPL. Clients are now able to ping one another between port 1 and 2, and after ~20 minutes of tests I haven't reproduced the CPU stall/clock reset issue yet.

Interesting. When I asked them if they planned to eventually remove the block, they said no. I guess the affected ISPs might have contacted them about it, or their sysadmin decided different from what their tech support thought.

No. I don`t expect a new GPL until May, except for the RT-BE92U (which is a special case), unless Asus changes the timeline they told me last time we discussed it.