LATEST: Do not upgrade, if you are using IPv6. There are issues not yet fully understood.
After waiting about 1½ year a new firmware release is made available.
The upgrade process from 1.0.4.17 did not run as simple as described in the release notes. I followed the instructions, but ended up with a device, which did not handle IPv6. After some twiddling with saving unchanged settings I managed to make it respond to a ping6, but not to route IPv6 through my tunnelbroker tunnel.
As an attempt to fix it I decided to select the IP4-option with the intent to revert to the dual-stack IPv4 and IPv6 again.
After the reboot I ended up with a router displaying only
$| trStrings["11383"] or 'i18nHTMLMissing' |$
on the web interface and did nothing but reply to pings.
After a factory reset (Press the red reset button for 10+ seconds and login with cisco/cisco) I restored the 1.0.4.17 configuration from a backup taken before the upgrade and the router returned to full operation again, it seems.
However, the IPv6 has now stopped working again. No response on ping6 and no routing.
The release notes are interesting. It is of course fine, that some errors in an option in DHCP is fixed, but a number of bugs reported 1½ year ago are still present and not at all acknowledged in the 'Known issues" section of the release notes. Apparently the development department is living in another world.
Just to mention a few:
- hairpinning is not fixed. The source IP address is still the router's IP address
- reordering access rules can still only be made within one page
- front lights are fixed and do not indicate amount of traffic
- RIP1 is announcing a WAN of /8 when it should only be /30
- SNMP is not using the standard Cisco prefix 1.3.6.1.4.1.9 for private fields
