What's new

R7800 telnet issue... Any ideas?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Tom Brough

Regular Contributor
Hello all, like the title says, got a R7800 running the latest voxel firmware and kamoj v3 add on, saw the new v4 released so tried to update but I can't access telnet?? It's on in the debug menu but I keep getting this strange nonsense instead, anyone got any ideas?

"
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
SSH-2.0-dropbear_2018.76


�y>9MI����_��curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,kexguess2@matt.ucc.asn.aucdsa-sha2-nistp521,ssh-rsa=aes128-ctr,aes256-ctr,aes128-cbc,aes256-cbc,3des-ctr,3des-cbc=aes128-ctr,aes256-ctr,aes128-cbc,aes256-cbc,3des-ctr,3des-cbc$hmac-sha1-96,hmac-sha1,hmac-sha2-256$hmac-sha1-96,hmac-sha1,hmac-sha2-256zlib@openssh.com,nonezlib@openssh.com,none����l�E��
 
If you getting telnet issue, and unable to enable Telnet, Follow below few steps:

  • Open any browser and type 192.168.1.1/debug.htm in address bar
  • Enter username password
  • Next window displays, Select Enable telnet check box
  • Now keep enjoy and do not forget to turn off telnet afterwards.
 
Hello all, like the title says, got a R7800 running the latest voxel firmware and kamoj v3 add on, saw the new v4 released so tried to update but I can't access telnet?? It's on in the debug menu but I keep getting this strange nonsense instead, anyone got any ideas?

"
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
SSH-2.0-dropbear_2018.76


�y>9MI����_��curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,kexguess2@matt.ucc.asn.aucdsa-sha2-nistp521,ssh-rsa=aes128-ctr,aes256-ctr,aes128-cbc,aes256-cbc,3des-ctr,3des-cbc=aes128-ctr,aes256-ctr,aes128-cbc,aes256-cbc,3des-ctr,3des-cbc$hmac-sha1-96,hmac-sha1,hmac-sha2-256$hmac-sha1-96,hmac-sha1,hmac-sha2-256zlib@openssh.com,nonezlib@openssh.com,none����l�E��

Such message you've got just means that you are using port 22 for telnet. Port 22 is a standard port of SSH but not telnet. Telnet port is 23.

Try to use port 23. In putty or from Windows command line:

telnet 192.168.1.1 23

Voxel.
 
Something must have changed in an app update as I'm using a mobile app to access telnet, and it's a saved connection I've used loads in the past, but your right I just looked and it's port 22, changed it to 23 and it works again.

Thanks voxel.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top