OpenWrt Forum Archive

Topic: wrt54g can't telnet or ssh

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

Hi,
I had a Linksys WRT54G (ver 1.0) bought a while ago.  Had assigned it a local address 172.16.0.68.  Had set up admin password, encripted wireless trasmission etc., until a week ago I decided to go for openwrt, because I was excited about it that it will give me the flexibility of a linux system.

I followed the documentation, downloaded the white russian openwrt for pppoe, sqash FS and followed the recommended way to flash using the Linksys web-interface and flashed the router.  The flashing was successful.  One thing I didn't (and couldn't do) was to set the boot_wait.   Searched the router documentation, but couldn't find a way to do it.

Now, I cannot login.  I can ping well.  However, neither telnet nor ssh work.  I am immediately kicked out with a message:

telnet: connect to address 172.16.0.68: Connection refused.

I try ssh and the same again:

ssh: connect to address 172.16.0.68: port 22: Connection refused.

I think that reflashing wouldn't help.   I don't remember closing any ports on the router previously with the default linksys firmware.  However, I did have encription enabled on the wireless interface with strict mac address checks.

The router seems to boot well, with Power (green) and Diag (red) light coming ON and then after about 10 secs the DMZ (green) light switch comes on, followed by Link (green) and a couple of blinks on Act.  Finally, the power, link and top light in the internet box stay on.   I have connected it to the up-link ethernet interface and I can ping it well without any loss of packets.

I searched the forum posts for similar problems.  Couldn't find any so far.

Can somebody out there help me?
Thanks in advance.

Failsafe mode is your friend. See the sticky thread here in this forum...

Thank you Forum2006.
I looked into the sticky thread.  But I couldn't figure out how to boot into fail-safe mode.

Can you or anybody else send me a link to the docs.
Thanks

m_osgood wrote:

I looked into the sticky thread.  But I couldn't figure out how to boot into fail-safe mode.

How should we write it, so that everybody understands it?

It's so easy...

hi

i installed openwrt on my linksys wrt54gl box.
boot_wait on, password set ,ping goes to the router's adress, can telnet the router before boot  but can't ssh to the router from my PC after boot.after boot i have the web page, and can ping the router.
i have the message
remote host identification changed
!
!
!
!
RSA host key for 192.168.1.1 has changed.

Please any help.

aniams wrote:

i have the message
remote host identification changed
RSA host key for 192.168.1.1 has changed.

Please any help.

the problem is on the pc side. Every ssh server has its host-keys, these are used to identify the server, to avoid man-in-the-middle attacks. If this changes, most ssh clients refuse to connect, until you manually acknowledge that the key has changed, or you remove the key from the clients known_hosts, depending on the client. You probably had another ssh server running on that 192.168.1.1 address, that's why you have the other key. In case of openssh, the known_hosts file is in ~/.ssh, this is where you need to delete that line containing 192.168.1.1, again not on the router, on your pc.

The discussion might have continued from here.