From owner-freebsd-current Sun Jul 30 04:55:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id EAA05326 for current-outgoing; Sun, 30 Jul 1995 04:55:52 -0700 Received: from crash.cts.com (crash.cts.com [192.188.72.17]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id EAA05318 for ; Sun, 30 Jul 1995 04:55:50 -0700 Received: from io.cts.com by crash.cts.com with smtp (Smail3.1.29.1 #5) id m0scWy1-0001YwC; Sun, 30 Jul 95 04:55 PDT Received: (from root@localhost) by io.cts.com (8.6.11/8.6.9) id EAA01318; Sun, 30 Jul 1995 04:55:40 -0700 From: Morgan Davis Message-Id: <199507301155.EAA01318@io.cts.com> Subject: Re: Clunky telnet/rlogin performance To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Date: Sun, 30 Jul 1995 04:55:39 -0700 (PDT) Cc: cml@aureus.mother.com, current@freebsd.org In-Reply-To: <199507300821.BAA27625@freefall.cdrom.com> from "Justin T. Gibbs" at Jul 30, 95 01:21:57 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 435 Sender: current-owner@freebsd.org Precedence: bulk Justin T. Gibbs writes: > > Much easier fix: > > vi /etc/sysconfig > > tcp_extensions=NO > > If this does fix the problem, I'd like to know why. Is BSDI's implementation > of RFC1323 and RFC1644 broken or is ours? Anyone know of some BSDI 2.0 > machines that we can test against? In fact, it fixed the problem most execellently. I wonder now, however, what I've lost in performance by having to set that up to tcp_extensions.