Hi there,
I have these devices with improved security which now I can't access through an iTest SSH session. I think the cyphers are not compatible and I get this error:
Unable to connect to 192.168.1.1. Reason:Failed to negotiate a transport component [ecdh-sha2-nistp256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp384,ecdh-sha2-nistp521] [curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group14-sha256,kexguess2@matt.ucc.asn.au] [Unknown cause]
I believe this error means, the devices are waiting for the cipher protocols: curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group14-sha256,kexguess2@matt.ucc.asn.au while iTest allows: diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521
Anyone has faced this before? Thanks!
Continuing test execution when SSH login fails 1 Answer
Is there a way to conditionally include steps in the Test Report from a variable 2 Answers
SSH Authentication failed. 3 Answers
What is the maximum number of SSH session that itest can run in parallel? 1 Answer
file session remote file URI 3 Answers
Copyright 2008- Spirent Communications, all rights reserved. Terms and Conditions.