From owner-freebsd-current  Fri Mar 31 00:13:46 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA28827 for current-outgoing; Fri, 31 Mar 1995 00:13:46 -0800
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA28815 for <current@FreeBSD.org>; Fri, 31 Mar 1995 00:13:44 -0800
Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB)
	id AA24012; Fri, 31 Mar 1995 10:13:33 --100
Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1)
	id AA00934; Fri, 31 Mar 95 10:13:25 +0200
To: current@FreeBSD.org
Subject: Re: rfc 1323 Support 
In-Reply-To: Your message of Thu, 30 Mar 1995 16:41:29 -0800
Date: Fri, 31 Mar 1995 10:13:24 +0200
Message-Id: <933.796637604@utis156.cs.utwente.nl>
From: Andras Olah <olah@cs.utwente.nl>
content-length: 860
Sender: current-owner@FreeBSD.org
Precedence: bulk

On Thu, 30 Mar 1995 16:41:29 -0800, "Justin T. Gibbs" wrote:
> David just uncovered the problem that has prevented me from talking to 
> other -current machines from behind my slip connection.  It seems that
> either the VJ header compression implementation in FreeBSD or that of
> the annex I use is not up to snuff with rfc 1323.  The cure to all
> of my problems was to do a:
> 
> sysctl -w net.inet.tcp.rfc1323=0
> 
> I will be talking to the annex gods here at Cal to see what they have to
> say about this, but even if it is an annex problem not a FreeBSD SLIP
> problem, should this stuff be enabled by default?

This problem has just recently been discussed on comp.unix.bsd under
the subject line: `BSD newtworking kills terminal server !'  A
posting from Michael L. VanLoon indicated that he already got a
patch for a Xyplex terminal server.

Andras