From owner-freebsd-net@FreeBSD.ORG Wed Jun 15 14:08:11 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 DF73A16A41C for ; Wed, 15 Jun 2005 14:08:11 +0000 (GMT) (envelope-from jeffm@frob.org) Received: from triton.genwebhost.com (triton.genwebhost.com [209.9.226.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id B46D543D1F for ; Wed, 15 Jun 2005 14:08:11 +0000 (GMT) (envelope-from jeffm@frob.org) Received: from jmeegan by triton.genwebhost.com with local (Exim 4.43) id 1DiYYs-0002Iq-IY for freebsd-net@freebsd.org; Wed, 15 Jun 2005 10:08:10 -0400 Received: from 130.76.32.15 ([130.76.32.15]) (SquirrelMail authenticated user jeffm@frob.org) by www.frob.org with HTTP; Wed, 15 Jun 2005 10:08:09 -0400 (EDT) Message-ID: <27188.130.76.32.15.1118844489.squirrel@www.frob.org> In-Reply-To: <79722fad05061505141b3ddb4c@mail.gmail.com> References: <58397.148.122.180.9.1118829978.squirrel@mail.yazzy.org> <79722fad05061505141b3ddb4c@mail.gmail.com> Date: Wed, 15 Jun 2005 10:08:09 -0400 (EDT) From: jeffm@frob.org To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - triton.genwebhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [32337 32338] / [47 12] X-AntiAbuse: Sender Address Domain - frob.org X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Looking for networking solution. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 14:08:12 -0000 > On 6/15/05, M.Jessa wrote: > Hi guys. > > I am looking for solution I could implement on a link with a huge > latency I am only familiar with split connection gateways. They totally isolate TCP from the effects of the satellite link by using some sort of enhanced protocol over the middle hop. The end TCPs are terminated locally and do not see large RTTs or latency. I did some work last year with Mitre's reference implementation of SCPS-TP, which made a huge difference. However, splitting the TCP connection does cause some issues. jeff