openssh bugs - Oct 2004 - [Bug 845] Received disconnect from ???: 2: Corrupted MAC on input.

http://bugzilla.mindrot.org/show_bug.cgi?id=845





------- Additional Comments From admin at different-perspectives.com  2004-10-25
23:56 -------
My three haporth worth ... this appears to be a common problem, having 
searched the internet for this error message.  I was also receiving this 
error, and believe I have fixed it ...

The WinXP laptop I am using to connect to the Linux file server using X Window 
has two addresses (and so two DNS names), one for cable and the second for 
wireless.  If the machine name does not correspond to the DNS name of the 
network interface, I get this error.  If I change the machine name so 
everything matches the error doesn't occur.  Repeatedly changing the machine
name is a big pain ...

Using either OpenSSH 3.9p1 under Cygwin or PuTTY 0.55 to connect to OpenSSH 
3.5P1 on SuSE Linux 8.2.  Same error with both.

If you tell me what logs and configs you want, I can send them ...



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=845





------- Additional Comments From admin at different-perspectives.com  2004-10-26
23:05 -------
My apologies ... spoke too soon.  Not getting bad MAC now, but instead getting 
Disconnecting: Bad packet length 3428026913.

Same result.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=845





------- Additional Comments From dtucker at zip.com.au  2004-11-23 16:54 -------
rapier at tyranny com about reports tracking down another cause of these errors:

"Anyway, the problem we found with the corrupted mac on input was a result
of
what seems to be a hardware bug in intel e1000 drivers. we since switched to
sysconnect cards and the problems went away (only to be replaced by another one
thats caused by a memory resources starvation issue when the system is under
high IO loads). Basically, the HMAC stuff seems pretty rock solid so if people
see this sort of error consistantly they should probably look at the drivers,
hardware, or cabling."



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.