Recent content by RMerlin

Gl.INet statement: https://www.gl-inet.com/blog/glinet-statement-on-recent-fcc-regulatory-developments/

We'd need to see the total block count shown above, to determine how much of it is actually used by the existing partitions.

Check the partition table. fdisk -l /dev/mmcblk0

SQ is for test purposes (Software Qualification or something like that).

They`re in the standard order: wl0: 2.4 GHz wl1: 5 GHz wl2: 6 GHz I think the GT-AXE16000 was the only one with things out of order.

Off-topic for this release thread. Already discussed in this other thread: https://www.snbforums.com/threads/us-bans-sale-of-all-new-model-non-us-made-wifi-routers.96974/

Not quite. They just ask you if you are a legal adult, as some of their services require the consenting from an adult. I bet such a question is often buried within general EULAs as well, as you can`t ask to a 12 years old to consent to a EULA binding.

Again, all are generic "we improved security" mentions, so I have no idea what the changes are, when they were applied by Asus, or what their importance are. These notes are partly written by an AI summarizing the changes between two releases. So sometimes, a changelog entry just summarizes...

Totally real, this has been discussed within the tech circles a few months ago when it was first announced. The website content has been through a few changes since the initial announcement, some of their initial claims were even more outlandish, they have been since removed.

This is way too vague, this doesn`t tell me anything. If the issue was in AiCloud for instance, then I don`t care - I completely removed AiCloud a few releases earlier.

None has appeared yet on the FCC public database AFAIK, unless that website is out of date - been a while since I've last monitored it. I'm only starting to see traces of Wifi 8-related code appear in the GPL sources, so it's probably still way too early. Politicians themselves probably don't...

Reproduce the issue with the stock firmware, then contact Asus. I have done all that I could, and since mine no longer crashed after that GPL update, there`s notthing more that I can do. They fixed it because I reported it to them a few weeks ago. I couldn`t integrate the fix myself because...

It's a CMS caching issue. While my deployment script does purge the Cloudflare cache through the API, my website has some custom modules that I wrote to dynamically display version/hash values on the website from data files that my deployment uploads. I forgot to purge the CMS cache after...

And restricted to specifically the FCC decision and the effect it will have on routers.

I don't know off the top of my head everything that tmight trigger a firewall restart, but there are a few events such as a WAN restart. Check the log for any mention of a "restart_firewall" event.