Date: Sun, 29 Aug 93 04:30:06 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #221
To: tcp-group-digest
TCP-Group Digest Sun, 29 Aug 93 Volume 93 : Issue 221
Today's Topics:
NOS in NT VDM
tcp syndata (4 msgs)
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Sat, 28 Aug 1993 21:12:06 -0500 (EDT)
From: djt@hoccny.ho.att.com (David J.Trulli)
Subject: NOS in NT VDM
To: tcp-group@ucsd.edu
I tried to run JNOS107b under NT in a DOS VDM.
I tried this with an empty autoexec.nos file and
find that NT reports an illegal instruction at
CS:0000 IP:00A8 OP:f004b5cbb8
This occurs before any output to the screen. I think is occurs
when NOS set up a new proc but I am not sure yet.
Before I start debugging this has anyone tired this yet ?
Dave
--
Dave Trulli djt@hogpa.att.com or David.J.Trulli@att.com
AT&T Bell Laboratories 908-949-3185
101 Crawford Corner Road
Room 3L-410
Holmdel NJ. 07733
------------------------------
Date: Sat, 28 Aug 93 16:46:17 EDT
From: ron@chaos.eng.wayne.edu (Ron Atkinson - N8FOW)
Subject: tcp syndata
To: tcp-group@ucsd.edu
Is tcp syndata something standard or is it something that should be
avoided? Wondering how legal it is to send data on the syn frames.
It has always worked fine for me and the packet <> internet gateway here,
but recently someone switched one of the SunOS systems over to Solaris and
now SMTP messages won't work with NOS. The Solaris system gets a protocol
error when it sees data on the syn frames.
Would like to know who should get the gripes, NOS or Solaris :-)
Ron N8FOW
------------------------------
Date: Sat, 28 Aug 1993 19:04:44 -0400
From: "Louis A. Mamakos" <louie@NI.umd.edu>
Subject: tcp syndata
To: ron@chaos.eng.wayne.edu (Ron Atkinson - N8FOW)
Sending data in a TCP segment along with a SYN flag is completely legal. The
Solaris system should either ACK the SYN's sequence number and ignore the
data, or ACK the SYN as well as the associated data. It sure sounds like
the Solaris end is broken, in the absense of any other information.
louie
wa3ymh
------------------------------
Date: Sat, 28 Aug 1993 20:18:18 -0600 (CDT)
From: lcz@dptspd.sat.datapoint.com (Lee Ziegenhals)
Subject: tcp syndata
To: tcp-group@ucsd.edu
> Is tcp syndata something standard or is it something that should be
>avoided? Wondering how legal it is to send data on the syn frames.
> It has always worked fine for me and the packet <> internet gateway here,
>but recently someone switched one of the SunOS systems over to Solaris and
>now SMTP messages won't work with NOS. The Solaris system gets a protocol
>error when it sees data on the syn frames.
> Would like to know who should get the gripes, NOS or Solaris :-)
This is a bug in SVR4, so I suspect Solaris is the same. It has been a
frustration for me in the past, as we use SVR4 on almost all of our Unix
systems at work. I can't do TCP between them and any NOS node that has
syndata enabled.
------------------------------
Date: Sat, 28 Aug 93 19:19:23 -0700
From: karn@qualcomm.com (Phil Karn)
Subject: tcp syndata
To: louie@NI.umd.edu, ron@chaos.eng.wayne.edu
I made sending data along with a SYN a configurable option in NOS
precisely because there are some other TCPs that are broken. They
should accept data with a SYN, but they don't.
Another reason to flush Solaris...
Phil
------------------------------
End of TCP-Group Digest V93 #221
******************************
******************************