Gargoyle Forum

Damn!

I just installed gargoyle on a new TP Link WR1043ND. It rebooted into Gargoyle, I logged on as admin, changed password etc.

Instead of re-entering all my channel settings, static ip's etc I thought I'd apply the settings from WRT54GL. Dumb move it seems. Gargoyle gave the message that the settings were successfully applied and that was that. I can't connect anymore (using web interface and 192.168.1.1). I've tried hard resetting the router by holding in the reset button, but the thing doesn't reboot or reset.

My WRT54GL is running 1.3.10. On the TP Link I installed gargoyle_1.3.14-ar71xx-tl-wr1043nd-v1-squashfs-sysupgrade.bin.

It doesn't respond to pings on 192.168.1.1.

Have I bricked the thing or is there any way of getting back to a working router?

Any help much appreciated.

I had something similar happen to me when I restored settings from a previous version of Gargoyle on an Asus WL-500g V2 to a newer version of Gargoyle. But I think I fixed it through flashing a new firmware on through telnet but I'm not quite sure.

OK. I now have found a way to get it to respond to a ping, using the 'repeatedly pressing the qss button' method from this thread.

http://forums.whirlpool.net.au/archive/1583722

Any advice on recovering it now ?

Install PuTTY and go to your routers IP and login as "root" and then whatever your usual password is and see if you have access

Thanks foreverstorm. Didn't see your post before.

I don't seem to be able to telnet.

When I try telnetting I get -

telnet 192.168.1.1
Trying 192.168.1.1...
telnet: Unable to connect to remote host: Connection refused

OK. Good news. I now have telnet access. I had to specify port 23. It looks like I may be getting somewhere now. Further help will be much appreciated. -

telnet 192.168.1.1 23
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.

=== IMPORTANT ============================
Use 'passwd' to set your login password
this will disable telnet and enable SSH
------------------------------------------


BusyBox v1.15.3 (2011-05-07 17:48:26 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
Backfire (10.03.1-RC5, unknown) --------------------------
* 1/3 shot Kahlua In a shot glass, layer Kahlua
* 1/3 shot Bailey's on the bottom, then Bailey's,
* 1/3 shot Vodka then Vodka.
---------------------------------------------------
root@(none):/#

Try "mtd -r erase rootfs_data"

Should erase all the settings you made and bring you back to the default.

Beautiful. That did it. Whew! Sigh of relief. Thanks so much for all the help.

Remember to not restore settings from different hardware. All the chip-related features (switch ports for example) depends on the hardware model and will cause such behaviour

May I suggest putting a warning about this on the "restore configuration" page of the interface?