SSH 断管，消息验证码不正确

Question

我已经设置了一个 Ubuntu 服务器，我打算用它来备份我的 macbook air rsync。但是每次我使用rsync，甚至是scp，连接都会断开，并出现以下错误之一：

packet_write_wait: Connection to 192.168.1.202: Broken pipe
packet_write_poll: Connection to 192.168.1.202: Broken pipe
packet_write_poll: Connection to 192.168.1.202: Protocol wrong type for socket

现在我已经搜索了其他类似的问题，通常人们会遇到会话超时的长备份问题。对我来说，这总是在开始文件传输后 10 秒内发生。我在使用 scp 和 rsync 时遇到了同样的错误。我想这可能是由于网络连接错误造成的，但我发现很难相信我与同一 LAN 上的服务器的连接如此不稳定。谁有想法？

我使用的导致错误的命令示例：

scp -r /Users/Matt/Documents matt@192.168.1.202:/media/matt/MattsBackups/

/usr/local/bin/rsync -av -e ssh /Users/Matt/Documents matt@192.168.1.202:/media/matt/MattsBackups/

我今天做了更多的测试，奇怪的是它在我的 LAN 之外工作得相当可靠。所以我从我的家庭网络内部再次尝试，它仍然不起作用。

跑步

grep 'sshd' /var/log/auth.log

在服务器上显示以下错误

fatal: ssh_dispatch_run_fatal: Connection from <My IP> port 49870: message authentication code incorrect

关于我的设置的一些更详细的信息：

Macbook Air OS X 10.11.5
OpenSSH_6.9p1, LibreSSL 2.1.8
rsync  version 3.1.2  protocol version 31

Ubuntu Server
OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips  1 Mar 2016

我确实注意到 ssh 版本的差异，但我希望这不会成为问题。我可以尝试使用自制软件安装更新版本。

更新：

好的，我刚刚用自制软件将 ssh 更新为

OpenSSH_7.2p2, OpenSSL 1.0.2g  1 Mar 2016

这似乎与 Ubuntu 机器上使用的版本相同。但是，当我运行命令时，Rsync 仍然会导致错误。这是我尝试使用 ssh -v 标志的命令：

/usr/local/bin/rsync -a -e '/usr/local/bin/ssh -v -c aes128-ctr -m hmac-sha1' /Users/Matt/Documents matt@192.168.1.202:/media/matt/MattsBackups/

输出是：

OpenSSH_7.2p2, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /usr/local/etc/ssh/ssh_config
debug1: Connecting to 192.168.1.202 [192.168.1.202] port 22.
debug1: Connection established.
debug1: identity file /Users/Matt/.ssh/id_rsa type 1 
debug1: key_load_public: No such file or directory
debug1: identity file /Users/Matt/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/Matt/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/Matt/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/Matt/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/Matt/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/Matt/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/Matt/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu1
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.202:22 as 'matt'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:+zkrXNJENs5EobFwHa8wpMDe6zPDfj975qLcPp4b4sg
debug1: Host '192.168.1.202' is known and matches the ECDSA host key.
debug1: Found key in /Users/Matt/.ssh/known_hosts:1
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/Matt/.ssh/id_rsa
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.1.202 ([192.168.1.202]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Sending command: rsync --server -logDtpre.iLsfxC . /media/matt/MattsBackups/MacAir/
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
Connection to 192.168.1.202 closed by remote host.
Transferred: sent 145304, received 13032 bytes, in 0.1 seconds
Bytes per second: sent 1373019.8, received 123143.2
debug1: Exit status -1
rsync: [sender] write error: Broken pipe (32)
rsync error: error in socket IO (code 10) at io.c(820) [sender=3.1.2]

Answer 1

作为最后的手段，我从 Windows 98 PC 上找到了一个旧的 10/100 以太网卡，并将其安装在服务器中。配置后，我没有更多的错误，超过大约 30 GB 的数据。我猜内置的以太网芯片组不能很好地与 ubuntu 配合使用。或者我以某种方式错误地配置了它。

编辑：虽然我从未找到问题的根本原因，但请务必查看@sourcejedi 答案下的评论线程。非常感谢@sourcejedi、@sneep 和@dentarg。