From owner-freebsd-net  Wed Sep 11 13:27:54 2002
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1586F37B400
	for <freebsd-net@FreeBSD.ORG>; Wed, 11 Sep 2002 13:27:52 -0700 (PDT)
Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B853E43E4A
	for <freebsd-net@FreeBSD.ORG>; Wed, 11 Sep 2002 13:27:51 -0700 (PDT)
	(envelope-from jayanth@yahoo-inc.com)
Received: from milk.yahoo.com (milk.yahoo.com [216.145.52.137])
	by mrout3.yahoo.com (8.11.6/8.11.6/y.out) with ESMTP id g8BKRh953271;
	Wed, 11 Sep 2002 13:27:43 -0700 (PDT)
Received: (from root@localhost)
	by milk.yahoo.com (8.11.0/8.11.0) id g8BKRgr87668;
	Wed, 11 Sep 2002 13:27:42 -0700 (PDT)
	(envelope-from jayanth)
Date: Wed, 11 Sep 2002 13:27:42 -0700
From: jayanth <jayanth@yahoo-inc.com>
To: Mike Silbersack <silby@silby.com>
Cc: kfl <kfl@xiphos.ca>, freebsd - net <freebsd-net@FreeBSD.ORG>
Subject: Re: T/TCP and FreeBSD 4.5
Message-ID: <20020911132742.C61572@yahoo-inc.com>
References: <JCEDLMKGMLLELHAJNIHJCEBJDGAA.kfl@xiphos.ca> <Pine.BSF.4.44.0209111604450.42163-100000@niwun.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <Pine.BSF.4.44.0209111604450.42163-100000@niwun.pair.com>; from silby@silby.com on Wed, Sep 11, 2002 at 04:09:31PM -0400
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org

Mike Silbersack (silby@silby.com) wrote:
> 
> Ho ho, ok, now to the real answer.  In order to make the syn cache more
> resistant to denial of service attacks, one of its features is that it
> will not accept any data in the initial SYN packet.  In 99.9% of the
> cases, this is fine, as TCP stacks don't tend to send data along with a
> SYN.  I guess T/TCP differs, though...

You are right, however this should happen only on the first connection,
between two hosts. All subsequent connections should behave normally
as there will be a cached route between these two hosts. 

Try running multiple connections between the same two hosts and you
should see subsequent ttcp connections behave normally.

jayanth

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message