1. Traffic Monitor is not accurate. While a torrent transfer was in progress I witnessed none of the traffic being counted.
Traffic Monitor has always been a PITA. Asus did additional fixes in 376.2769, no idea if resolves any of the remaining issues however. So far I'm unable to reproduce any of the reported issues, as they only occur under very specific scenarios.
2. Scheduling a disk scan does not work.
Known issue in Asus's code, it has never worked AFAIK, and I'm letting Asus take care of this one.
3. Not sure why, but I lost the ability to update my asuscomm.com DDNS hostname that I have maintained for years. This was a BIG issue as a lot of things have been set up using that hostname, but I learned from my mistake and started an account with no-ip going forward. The services would say registration successful but the IP would never update. It allowed me to register a new hostname successfully. This hostname is permanently lost...
Asus's DDNS uses your MAC to authenticate itself (otherwise anyone could steal your hostname). It's normal that changing router will prevent you from reusing it with a new router, nothing that can be done about it.
4. After a clean flash of the firmware, an OpenVPN server will show as running. Though I can disable it successfully.
Known issue, that's because when Asus took my OpenVPN code and added it to the stock firmware, they changed the way the enable nvram setting works from my original code. So any time someone upgrades from stock firmware to my firmware without a factory default reset, the OpenVPN server will be enabled.
Changing this will create other issues (such as people who never read the changelog would then start reporting that "my OpenVPN no longer start automatically, must be broken", that's why I haven't done anything about this yet. If it starts becoming a common issue (Asus changing the behaviour of existing nvram settings), I might just start requesting that people switching from stock to modded firmware do a mandatory factory default reset afterward. I do my best to keep 100% backward and forward compatibility, but when it's Asus breaking things, there's nothing I can do about it.
5. I can no longer connect to network resources from the LAN side of the router using the DDNS hostname. For instance I used to be able to connect to servers on my network using the DDNS hostname and port forwarding rules (
https://hostname.ddns.com:8085/ which would translate to
https://webserver/)
NAT loopback is working fine here, and every time I had a report of NAT loopback not working, I would spend time re-re-re-retesting it for the 100th time to confirm that it does work fine. And then the reporter realizes that the issue is his DDNS not being up-to-date, forwarding to the wrong IP, or his target service having a firewall blocking access to it... So most likely your issue is with one of these - double check the DDNS and the target forward.
6. Using the MAC clone feature on the WAN will eventually result in internet traffic from the LAN side not reaching the WAN even though I can still ping internet addresses from the ping tools on the router management interface.
This is probably an ISP issue. ISPs can be picky if you play with your MAC, as they use it to ensure that they don't issue multiple leases to a given client.
