Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 7 Mar 2010 14:57:17 -0800
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Tim Kientzle <kientzle@freebsd.org>
Cc:        "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Subject:   Re: Wireless TCP aborts
Message-ID:  <20100307225717.GB1218@michelle.cdnetworks.com>
In-Reply-To: <4B9425C4.5060309@freebsd.org>
References:  <4B9425C4.5060309@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 07, 2010 at 02:16:36PM -0800, Tim Kientzle wrote:
> Using ssh and rsync to copy a lot of stuff from my
> old desktop to my new laptop.  The old desktop is using
> a wired connection to an (admittedly crappy) D-Link router,
> the new one is using an Atheros wireless connection to the
> same router.  I periodically see the transfer fail with
> the following messages on the wireless side:
> 
>   Corrupted MAC on input.
>   Disconnecting: Packet corrupt

I guess this message came from ssh.

>   rsync: connection unexpectedly closed ... [receiver]
> 
> and then the rsync session is dead.
> 
> It seems odd that a single corrupt packet would terminate
> the TCP connection.
> 

I think it's default behavior of ssh if it detect malformed packet.
I used to see this forced disconnection of ssh when driver
incorrectly set RX checksum flag OK for corrupted packets which
were caused by hardware bug.

> uname: FreeBSD 9.0-CURRENT r201154M: Tue Dec 29 09:27:29 PST 2009



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100307225717.GB1218>