Recent content by hancox

Would be welcome news. QoS has been broken in a few models for years now, and very little dev effort seen on Asus part.

A Node de-attachment performs a reset itself, so this shouldn't be a problem. For this reason, I usually: 1) upgrade node via GUI 2) detach the node from GUI 3) re-attach node via GUI I've admittedly had some issues on occasion with the 5 band not accepting clients, which is usually...

I have found outright disabling roaming assistant makes overall roaming better. YMMV. (2 nodes in a rectangular house)

Given that they never fixed the AX-86U, i wouldn't have hopes here. I haven't even bothered to check if the AX6000 is any better - i don't trust ASUS here, at this point.

Sorry - total brain fart here in that I was expecting this to be the 3006 alpha moving to beta - not the 388 branch. Jeez.

Not seeing AX6000 in either download mount - am i missing something?

Let's show @RMerlin some love for patching multiple models before Asus!

I would have to think the venn diagram of people sophisticated enough to use 3rd-party firmware, and those who use a training-wheels type "cloud" service, has to be exceedingly small.

Forgot the air gapping risers.

AI Mesh node in an unattached garage forever - no issues, but band movements have relegated it to spare use. It makes one nice WIFI NIC for a device without WiFi, when needed.

"Code" and "GPL" are not the same - @Tech9 is correct here.

Me too. Owned one. It was a piece of junk that dropped WiFi repeatedly. I lost it to a lightning strike, and replaced it with an AX86S, which is better in every way.

Yep - saying same thing. As to this CVE - it appears to be related to Asus use of OpenVPN ( https://nvd.nist.gov/vuln/detail/CVE-2024-0401 ). Straight from the Merlin release notes for the latest version:

Not unreasonable. I get it. Just to set your mind at ease - unless @RMerlin has an explicit fix for a CVE (which isn't that common), his changelogs will only list a (usually somewhat aged) version upgrade to an underlying component, with no reference to any CVE. History and my gut this...

I wouldn't worry yet - overwhelming majority of similar vulnerability fixes, in the past, have been circumvented by Merlin being more up to date on non-firmware components. Just because Asus releases firmware, doesn't mean that the code they're fixing actually sits in the GPL