Recent content by RMerlin

No, it's only an issue if you enable and use it. The traffic monitor wouldn't really be of any use in an AP, monitoring would need to be done by the primary router itself.

That would require modifying the language dictionnaries, which I don't do: 1) I don't speak the 20+ languages supported by Asuswrt 2) It would make all future webui GPL merges a nightmare to handle So, anything that I write UI-wise and which does not already have an existing translated string...

More than cosmetical, the new UI is based on the Bootstrap toolkit, with some of the main dashboard UI elements being configurable. It should also make the UI more responsive (tho I never really tested it out on a smartphone). The older settings pages are handled by a wrapper, with some of the...

Stop believing these drunken AI chatbots, seriously... Also, you are 10 years late to this discussion.

It will be fairly similar to the UI of the Expertwifi models, which also have the Dashboard-based UI: https://demoui.asus.com/EBG15/index.html

Another year is almost gone, and I thought this year I'd have a go at my irregular "year in review" posts. It certainly has been an... interesting... year, globally. In the sense of that old "May you live in interesting times" expression. Not gonna lie, I'm not too optimistic about what 2026...

Final release is now available. Thanks to everyone who participated in this beta cycle.

Reserved post.

Asuswrt-Merlin 3004.388.11 is now available. The focus of this release is merging a new GPL (largely security fixes), the removal of AiCloud due to repeated security issues, and the new Traffic Monitor redesign that was initially introduced in 3006.102.6. Changes since 3004.388.10_2...

Removed pointless posts. OP: nobody is going to blindly analyze multiple hundred of logfile entries for you based on just a vague "Some things look suspicious". You will need to provide more accurate info and more specific lines that lead you to believe that, otherwise your post will be a...

No release notes because that is not a formal release, it's just a snapshot of the development code at that specific point in time.

If they are on a separate VLAN, then no - that's the whole point of using VLANs, to isolate networks.

Cleaned up thread from pointless repeated posts.

The information is not always provided by the driver, it depends on the SDK version.

Cables would be the next thing to check. There is also the possibility of a bad NIC. Weirdest issue I've experienced in my work was a customer's network going down every few minutes, lots of packet losses as well. By process of elimination I tracked down the issue to a bad NIC in an old...