Nothing was changed with regards to the WAN handling between 102.6 and 102.7.
merlin@ubuntu-dev:~/dev/amng$ git log --oneline 3006.102.6..3006.102.7
21d30a367f (tag: 3006.102.7) Bumped revision to 3006.102.7 final
7b6810ec20 Updated documentation
2bc9ee0923 rc: refresh wireguard BLOG bypass...
I don't have any info regarding the numerous revisions.
Asus did something similar with tthe RT-AX58U/RT-AX56U as well in the previous gen, which makes me wonder if it's inherent to these bcm67xx models. Perhaps they are just more agressively trying to reduce costs due to smaller profit...
Double check that you are indeed running the latest test build. The version at the top should report "3006.102.7_1-gbeea6c005a"
Mine still hasn't recrashed since the update, while previously it would crash within a few minutes after booting.
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.
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...
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.