I was fiddling with my RT-AC66U configuration. The last tweak was to upload my authorized_keys file to the Administration > System > SSH Authentication key dialog box and click Apply. At that point my RT-AC66U became non-responsive. It may be helpful to know that my router had a non-default LAN IP: 192.168.52.2.
The first thing I tried was to click the reset button on the back and then connect an ethernet cable, manually configure the ethernet port to 192.168.1.38 and http to 192.168.1.1. There was no response to either ping or http. I then reset the computer to DHCP and saw that it received an address on 192.168.52 from the router. Apparently the reset button had not changed the settings. I discovered that I could ssh into 192.168.52.2 and I went to ~admin/.ssh and deleted authorized_keys in case that was the problem. However, that did not fix the router; it still refused to respond to http on 192.168.52.2 after a power cycle. In fact a power cycle causes the authorized_keys file to reappear.
I attempted a Firmware restoration by powering off, pressing the reset button, and powering on, watching the power LED blink on and off every 10 seconds or so, and then using the utility downloaded from the ASUS website, but it says that that the router is not in rescue mode.
Is there something I can do from ssh to rescue the router? I have a .CFG file from about an hour before I started tweaking the configuration, so if there were some way to restore that, I should be in good shape, but without the http GUI, and I don't know how to do that.
Any ideas would be most appreciated!
The first thing I tried was to click the reset button on the back and then connect an ethernet cable, manually configure the ethernet port to 192.168.1.38 and http to 192.168.1.1. There was no response to either ping or http. I then reset the computer to DHCP and saw that it received an address on 192.168.52 from the router. Apparently the reset button had not changed the settings. I discovered that I could ssh into 192.168.52.2 and I went to ~admin/.ssh and deleted authorized_keys in case that was the problem. However, that did not fix the router; it still refused to respond to http on 192.168.52.2 after a power cycle. In fact a power cycle causes the authorized_keys file to reappear.
I attempted a Firmware restoration by powering off, pressing the reset button, and powering on, watching the power LED blink on and off every 10 seconds or so, and then using the utility downloaded from the ASUS website, but it says that that the router is not in rescue mode.
Is there something I can do from ssh to rescue the router? I have a .CFG file from about an hour before I started tweaking the configuration, so if there were some way to restore that, I should be in good shape, but without the http GUI, and I don't know how to do that.
Any ideas would be most appreciated!
