From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 02:20:46 2004 Return-Path: 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 C623116A4CE; Tue, 10 Feb 2004 02:20:46 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8859343D1D; Tue, 10 Feb 2004 02:20:46 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1AqUzs-000G9q-TH; Tue, 10 Feb 2004 12:20:05 +0200 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Andre Oppermann In-reply-to: Your message of Tue, 10 Feb 2004 11:11:12 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 2004 12:20:04 +0200 From: Danny Braniss Message-Id: cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 10:20:46 -0000 > I have been the last one fuzz around in the TTCP code areas. However > there could be problems that were lurking there before in other code > parts (syncache maybe). TTCP isn't used in production by anyone (AFAIK) > and only minimally tested. ahh, that's one realy good piece of info so far. this is one more step away from 'don't judge a book by it's cover' ... reading the specs of ttcp, it seemed promising, but i guess it becomes insignificat when the world uses ssl:-) > > What FreeBSD version are you using? 4.8, 4.9 and current. and solaris(but i guess they don't do ttcp) and linux (not yet). danny