From owner-freebsd-current  Sun Dec 31 00:01:36 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA12548
          for current-outgoing; Sun, 31 Dec 1995 00:01:36 -0800 (PST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA12543
          for <current@FreeBSD.ORG>; Sun, 31 Dec 1995 00:01:33 -0800 (PST)
Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelayMX-SVR4_1.2/RBINF)
	id JAA04556; Sun, 31 Dec 1995 09:01:25 +0100
Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB)
	id JAA12821; Sun, 31 Dec 1995 09:01:22 +0100
Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4)
	id JAA13558; Sun, 31 Dec 1995 09:01:21 +0100
To: current@FreeBSD.ORG
Subject: Re: -current TCP interoperability issues 
In-reply-to: Your message of "Fri, 29 Dec 1995 19:12:07 PST."
             <199512300312.TAA17438@precipice.shockwave.com> 
Date: Sun, 31 Dec 1995 09:01:20 +0100
Message-ID: <13557.820396880@curie.cs.utwente.nl>
From: Andras Olah <olah@cs.utwente.nl>
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

On Fri, 29 Dec 1995 19:12:07 PST, Paul Traina wrote:
> I'm having problems with tcp connections that contain data with SYN packets.
> It seems like turning off the TCP extensions is not sufficient.

It would be nice if you could send a tcpdump of how these connections
fail.  On the other hand, the handling of the TCP extension bits could
be more conservative in our TCP implementation.  Right now, we send data
on the SYN segment even if rfc1644=0, only the CC option is turned off.
In defense of the current mechanism, however, note that this is
perfectly valid TCP behavior.

Andras