OpenWrt Forum Archive

Topic: Bricking my WRT54G by mucking up ssh?

The content of this topic has been archived on 20 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I reluctantly abanded tftp in favor of ssh as the openwrt instructions suggest. I liked tftp because there was no password to loose.

I like being able to play with my router remotely but I'm thinking I should not have ssh running on port 22. Furthermore I should probably use a stronger password and move  from port 22 to something else less obvious. Someone said their port 22 gets attached every 2 minutes!

What is the consequence of forgetting a openwrt/ssh root password?  Or mucking up firewall.user to change the port from 22 to something else? According to http://forum.openwrt.org/viewtopic.php?id=4856 I have to edit /etc/init.d/S50dropbear too. What would happen if I did not get this correct? Would I brick my wrt54g that is now irreplacable? Or is there a reset button to restore the defaults?

Yikes!

Thanks,
Siegfried

Unless you are in a location where your wrt is only accessible via the public internet, why not just restrict ssh to the private network? For that matter, I don't even put a public address on my wrt's, but this requires dhcp and/or nat upstream and may not be feasible for the 'home' user.

What is the consequence of forgetting a openwrt/ssh root password?

Boot to failsafe
>mount_root
>passwd  (or just rm passwd)

- DL

(Last edited by dl on 19 Mar 2006, 00:54)

siegfried wrote:

I reluctantly abanded tftp in favor of ssh as the openwrt instructions suggest. I liked tftp because there was no password to loose.

tftp?  Or are you referring to telnet?

Cheers,
Martin.

The discussion might have continued from here.