rsync corrupted MAC
louie at transsys.com
Mon Oct 10 21:16:36 UTC 2011
On Oct 10, 2011, at 2:38 PM, Larry Rosenman wrote:
> On 10/10/2011 10:47 AM, John Baldwin wrote:
>> On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote:
>>> Any ideas on which side or what might be broke here?
>>> Corrupted MAC on input.
>>> Disconnecting: Packet corrupt
>>> rsync: connection unexpectedly closed (33845045 bytes received so far)
>>> rsync error: error in rsync protocol data stream (code 12) at io.c(605)
>>> rsync: connection unexpectedly closed (1450 bytes received so far)
>>> rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9]
>> I've had somewhat similar issues (ssh getting corruption in its data stream)
>> when a NIC in my netbook was corrupting packet data when it ran at 1G (it
>> worked fine at 10/100). Pyun eventually fixed the issue by applying enough
>> workarounds (it was likely a hardware bug in the NIC's chipset). However, it
>> wasn't easy to debug unfortunately. :(
> Any ideas on where to start?
> from the 8.2 box (tbh.lerctr.org in the script):
> 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet TEG-160WS Gig switch->9.0 box (borg.lerctr.org).
> So, where do I start?
I'd turn off IP / TCP / UDP checksum offloading on your NIC if it supports it, and see if you are getting network layer checksum errors. If the IP checksum is wrong, then it happened on the last hops between the NIC and memory or across the previous network hop.
More information about the freebsd-stable