From owner-freebsd-questions Tue Feb 4 14:20:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA17498 for questions-outgoing; Tue, 4 Feb 1997 14:20:16 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA17434; Tue, 4 Feb 1997 14:20:02 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA01750; Wed, 5 Feb 1997 09:19:42 +1100 (EST) Date: Wed, 5 Feb 1997 09:19:41 +1100 (EST) From: "Daniel O'Callaghan" To: Robert Chalmers cc: bsd , FreeBSD ISP Subject: Re: annex+sco, no worries, fbsd, yes In-Reply-To: <199702042151.HAA06076@nanguo.chalmers.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 5 Feb 1997, Robert Chalmers wrote: > Here's an interesting one. > > If I run SCO 3.2v4.2 + the Annex(V9.2), traffic flows now worries in both > directions. No problems with rfc1323 or anything else. > > Hook up the FreeBSD 2.2 + Annex(V9.2). Immediate problems. Anything that speaks > rfc 1323 has problems. (mostly Sun's and other FreeBSD machines it seems) > > Why is this? Is there a technical reason for this that anyone knows about? I thought we went through this. RFC 1323 extension data streams have SYN packets with data in them, at the connection setup. Annex OS v 9.x throws a fit when it sees a TCP packet with SYN set and actual data. Traditional TCP connections are setup using SYN/SYN-ACK packets with no data payload. Does SCO support RFC 1323 TCP extensions? Danny