The install went fine on an RT-N16, and I had a successful boot and usage for 24 hrs. During reconfiguration via web menu (of openvpn), bad settings were used somewhere, and after the save button was hit, the router no longer responds (web interface, ssh, telnet, even DHCP ip issuing). I tried putting it into recovery mode, but I can't get anything to resolve at 192.168.1.1. How does someone revert to the stock tomatousb install or is it bricked?
So someone else will learn from my adventure:
I got it to go into recovery mode and tftp would connect (but the web interface or anything else didn't). I suspect in hindsight that's a duh, but I missed that earlier. So I re-flashed it with the original trx file and rebooted after a few minutes and it started up.
Holding the reset button (not the Wireless used to get to recovery mode) on power up 'should' just reset the nvram via the CFE. Haven't tried it recently though!
I just did the same thing setting up the VPN server on my new RT-N16 and stupidly set the VPN subnet to the same as the router it did not like that!!!
But I beleave what got it to seeset to defaults was to unplug the power then hold down the WPS botton and then plugged the power in while still holding the WPS button. I then held the button for about 10 seconds with the power in and then let go and waited about a minute and then tried to get to the web admin page using the default IP and it was successfully restet to defaults….
2 ways to reset to defaults:
1. Hold the "Reset" button (not the "WPS" or "EZ Setup" button) for 5+ seconds, wait for the router to reboot. Unless router is bricked, it will work.
2. For Asus routers, hold the "WPS" (not the "Reset") button while powering up the router, wait until power LED stops flashing and the router reboots. For most other non-Asus routers, the so called "30-30-30" reset should work (not getting into the details of which part of it actually does the trick).
P.S. We should start the FAQ section on this site…..
I was expecting the WPS to reset the NVRAM and I'm not sure it did. Spent a good 30 minutes last night trying that, rebooting, failing, wash rinse repeat. I tried holding the recovery button on start up and it went to recovery (good), but when I held WPS for upwards of a full minute, it just kept blinking rapidly. Thats what I didn't understand. I suspect there was something in the series of events that I wasn't doing that everyone else does. :-/
On the positive side, it at least allowed me to tftp the trx file and just blow away the existing configuration. :-)
And yes, I did the same thing xerose did; set the VPN subnet to the same as the LAN and poof.