From owner-freebsd-questions  Tue Feb  4 20:50:05 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA00399
          for questions-outgoing; Tue, 4 Feb 1997 20:50:05 -0800 (PST)
Received: from databus.databus.com (databus.databus.com [198.186.154.34])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA00383;
          Tue, 4 Feb 1997 20:50:00 -0800 (PST)
From: Barney Wolff <barney@databus.com>
To: bsd <freebsd-questions@freebsd.org>, FreeBSD ISP <freebsd-isp@freebsd.org>
Date: Tue, 4 Feb 1997 23:45 EST
Subject: Re: annex+sco, no worries, fbsd, yes
Content-Type: text/plain
Message-ID: <32f811740.2bf3@databus.databus.com>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Date: Wed, 5 Feb 1997 09:19:41 +1100 (EST)
> From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
> 
> 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.

Er, 1323 does not send data in the SYN seg, but some extra options in
every seg.  It's T/TCP that sends data in the SYN seg.  And it wasn't
the SYN seg that got lost.

Irix supports 1323, dunno about T/TCP, dunno about SCO.

Barney Wolff  <barney@databus.com>