I was running the most current firmware avail at the time, and some of the same problems are present on the newer firmware too. These are some of the issues I have had, gripes, and things that don't seem to work correctly (they do work fine on other MFR's routers though.
Before switching to an alternate port & SSL internally and externally: takes me to http://router.asus.com...
when I browse to the internal IP of the router for config.
Can’t select an IP (to copy) with mouse in IE, OR Firefox, in Network,
Clients, View List, but when you think you have… it auto un-selects due to some
Icon changes for devices (Linux box, Windows Boxes, etc). randomly
doesn’t function. (Linux vs. Windows,
Vs. other… it detects wrong, and you can’t fix it if it does.) However “Sometimes” it does? Seems random, or maybe seeking SaMBa shares to autodetect if a Windows box, and if it sees them you can't seem to change it.
Can’t use 443 for external access to router, and 80 for
internal. Both http and https for both,
or one or the other. Other routers you can just enable and browse
to https://<whatevz> on the external but this does not work on 443, as it
is used by some other service that you may not even use, even if it is disabled.
For some reason the router thinks you just changed config if using Firefox browsing to ext. port of 8433 ( i.e. https://some.dyndns.org:8433 not mine, but example), OR (https://192.168.1.1) 433 internally. HOWEVER using: http://router.asus.com works for some reason.
Clients View List does not show all devices connected… randomly fails to list functioning network
devices that are pinging, even if you might have an an active ssh session to it, and
you know they are clearly on the network.
You cannot see which SSID clients are connected to, if you
are using multiple SSIDs (AKA guest wireless).
Removing/Disabling a Guest SSID causes wireless connections
to another Guest AND primary SSIDs to be disabled and subsequently disconnect when
the device enables whatever config you changed, whether it be wireless-related,
or something else.
Removing a Guest network SSID can sometimes make
the native SSID become one of the Guest SSIDs, seems random, but this is the
cause, as it has happened to me more than 3 times so far.