Asuswrt-Merlin 378.52 is now available for all supported models.
UPDATE: 378.52_2 is now available, resolving the following issues:
....
Hello Merlin,
I am new to Merlin's Firmware because I bought an ASUS RT-AC66U recently to replace my old, slow! but functional Linksys WRT54GS v4.
After playing around a lot with both the original firmware and various versions of your work, I installed the latest Firmware 378.52_2.
So far everything is working fine, however, I found two things:
1. Possibly a minor (cosmetic?) glitch: in the main screen (Network Map) the registered DDNS domain-name is no longer showed with the Internet Status.
In previous versions it did show the registered name (I used the ASUS way XXXXXXXX.asuscomm.com), but now it just shows "GO" like when it is not yet registered.
The registration DOES work however, it seems just a visual thing.
I use the DDNS in combination with DHCP reservation and port-forwarding to access our webcam remotely:
http://macisvenda.asuscomm.com:8899/snapshot.cgi?user=visitor&pwd=visitor
2. I use a (Chinese) Pipo M6 Pro running KitKat 4.4.2. This Android device had a perfect 2.4Ghz 54Gb connection when I used my old Linksys WRT54G.
But now, using the 2.4Ghz network set to everything AUTO it does connect , but after a short (random) time, it no longer will open webpages, a generic Time-Out message is shown in the browser. (I tested with Chrome, Firefox, Stock, ..)
Funny thing: if I run a 'Ping' to the same website, the ping will continue to run without any delay or dropout?
Any of my other devices does work perfect when I connect them to the 2.4GHz wifi.
I was thinking of a DNS fault, (or even EDNS) , I tried many different DNS-servers (my ISP, Google, etc)
Now I think it has to do with the Wifi getting "out-of-sync", it just will not work at higher speeds. (N-speeds are out of the question)
My workaround for now is to set the 2.4GHz to 'Legacy at 20MHz', this way this tablet seems to be able to maintain a functional web-browser.
My other devices use mainly the 5Ghz, or a wired connection.
However, I think this maybe an ASUS thing, because the exact same behavior is shown with different versions of the Stock ASUS firmware.
Thanks for you work,
Un saludo from Spain,
Satbeginner