R7800 telnet issue... Any ideas?

[Tom Brough]

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,[email protected],ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,[email protected],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,[email protected],[email protected],none����l�E��

 

[Gloria Williams]

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.

 

[kamoj]

Are you trying to run SSH from Putty?

Run step 1 to 4 from here instead:
https://www.snbforums.com/threads/k...800-x4s-and-r9000-x10-temperatures-a-o.55063/

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?

 

[Voxel]

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,[email protected],ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,[email protected],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,[email protected],[email protected],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.

 

[Tom Brough]

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.