From owner-freebsd-current@FreeBSD.ORG  Sun Nov 25 20:21:52 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 37E5816A420
	for <current@freebsd.org>; Sun, 25 Nov 2007 20:21:52 +0000 (UTC)
	(envelope-from silby@silby.com)
Received: from relay02.pair.com (relay02.pair.com [209.68.5.16])
	by mx1.freebsd.org (Postfix) with SMTP id C505513C461
	for <current@freebsd.org>; Sun, 25 Nov 2007 20:21:51 +0000 (UTC)
	(envelope-from silby@silby.com)
Received: (qmail 93002 invoked from network); 25 Nov 2007 20:21:50 -0000
Received: from unknown (HELO localhost) (unknown)
	by unknown with SMTP; 25 Nov 2007 20:21:50 -0000
X-pair-Authenticated: 209.68.2.70
Date: Sun, 25 Nov 2007 14:21:51 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <E1IvW8P-0000Kl-0v@clue.co.za>
Message-ID: <20071125142118.G6541@odysseus.silby.com>
References: <E1IvW8P-0000Kl-0v@clue.co.za>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Kip Macy <kip.macy@gmail.com>, current@freebsd.org
Subject: Re: TCP RST+data! 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Nov 2007 20:21:52 -0000


On Fri, 23 Nov 2007, Ian FREISLICH wrote:

> I see.  Playing around with net.inet.tcp sysctls, disabling delayed_ack
> fixes the problem with this phone.  Do you think that this is a bug
> in the phone's TCP stack?
>
> Ian

One more question I forgot to ask - does net.inet.tcp.rfc1323=0 help the 
situation at all?  Even if not, please send me a tcpdump of that as well.

-Mike