两者之间可以相互ping通,防火墙设置没有问题,但是无法ssh。 问题原因就是对应网卡设置的MTU值过大,数据包在传输的时候出现了错误。 解决方法windows下,管理员下运行cmd。 netsh interface ipv4 show subinterf…
在用osboxes.org上的linux ubuntu镜像时,安装了openssh-server后,发现ssh会卡在debug1: SSH2_MSG_KEXINIT sent上 解决方法是: $ sudo rm -rf /etc/ssh/ssh_host* $ sudo dpkg-reconfigure openssh-server
debug1: ssh2_msg_kexinit sent 是一条SSH(Secure Shell)客户端调试信息,表明SSH客户端已经向SSH服务器发送了一个密钥交换初始化(Key Exchange Initiation,简称KEXINIT)消息。在SSH连接过程中,密钥交换是建立安全连接的重要步骤之一,用于协商加密算法、哈希函数等安全参数。 可能导致这条调试信息出现的原因 正常的SSH连...
最近的MHA配置时碰到了Permission denied (publickey,gssapi-with-mic,password)这个错误提示，同时在使用...
Mac ssh "debug1: SSH2_MSG_KEXINIT sent" http://techbackground.blogspot.com/2013/06/path-mtu-discovery-and-gre.html 简单解释就是IPV4报头与GRE报头结构不同,导致GRE数据包最大内容载荷只有1454,默认mtu如果是1500的话,就会有46字节的内容无法处理导致错误。
debug1: SSH2_MSG_KEXINIT sent debug3: receive packet:type20 debug1: SSH2_MSG_KEXINIT received debug2:localclient KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sh...
SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ssh-ed25519 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha...
"OpenSSH for Windows" version v1.0.0.0-Beta Server OperatingSystem Windows 10 Pro Client OperatingSystem MacOS High Sierra 10.13.2 What is failing The connection is reset by the server after SSH2_MSG_KEXINIT sent by the client. I needed ...
SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ssh-ed25519 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha...