ssh disconnect

[K.C. Chan]

Disconnecting: Corrupted MAC on input.
debug1: Calling cleanup 0x8053410(0x0)
debug1: Calling cleanup 0x805b070(0x0)
debug1: channel_free: channel 0: client-session, nchannels 1
debug1: Calling cleanup 0x80674e0(0x0)


This happens when ssh into remote box and running commands.

[Steven E. Protter]

Seems like the remote box rebooted or hung.

Assume processing stopped, and is incomplete with all the ramifications of that status.

SEP

[Edwin Buck]

Linksys routers created a similar problem due to a "dumb" packet rewriting algorithim. If possible determine what equipment is between you and your server. They might share similiar chipsets / firmware.

It also might be useful to check your NIC's error and checksum counters.

Some people have reported that changing network drivers "fixed" this.

Try running the same command using the ssh -v option, as it will give more output (perhaps isolating it to a ssh keying problem)

There's an open bug for this at http://bugzilla.mindrot.org/show_bug.cgi?id=845
Some problems similar to this have been isolated to bad memory, cabling, hardware, etc. Adding comments to the bugzilla will speed it's isolation and closure.

[Edwin Buck]

Here's a link indicating that a specific Linksys firmware release can corrupt the Message Authentication Code (MAC) of openssh

http://msgs.securepoint.com/cgi-bin/get/openssh-unix-dev-0405/3/2/1/2.html

[Jan Sladky]

Hi,
I have tried to find something on the net and result is similar to Edwin's

http://mail-index.netbsd.org/port-macppc/2003/04/02/0001.html

Jan