Xref: utzoo comp.protocols.tcp-ip:6961 comp.dcom.lans:2747
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!rutgers!cmcl2!ccnysci!dan
From: dan@ccnysci.UUCP (Dan Schlitt)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans
Subject: Re: Telnet problems with Bridge CS/1's
Message-ID: <1805@ccnysci.UUCP>
Date: 1 May 89 14:56:00 GMT
References: <7502@charlie.OZ>
Reply-To: dan@ccnysci.UUCP (Dan Schlitt)
Organization: City College Of New York
Lines: 28

In article <7502@charlie.OZ> jgm@kokab.cc.deakin.OZ () writes:
:We have Bridge CS/1's and CS/200's running s/w version 20000 into
:Suns running SUNOS 4.0. The telnet client on the Bridge boxes
:passes a <CR><NUL> string (which is produced by the Suns as per
:the telnet protocol spec) to the terminal as is (i.e. without
:stripping the <NUL>). This upsets terminals which may use \015 as
:part of their cursor address sequence.
:
:Has anyone else seen this problem? Is there a fix for it? The
:Australian agents are mainly into XNS, and do not seem to
:understand the problem.
:
:John Moorfoot 		ARPA:	jgm%charlie.oz.au@uunet.uu.net
:			UUCP:	...!uunet!munnari!charlie.oz!jgm

We also have problems with Bridge telnet handling of <CR><NUL>.
On some versions of their software it is broken.  They know about it
but refuse to supply fixed software.  More recent versions are capable
of doing the "right thing".  It is configurable in case you want to do
the wrong thing.



-- 
Dan Schlitt                        Manager, Science Division Computer Facility
dan@ccnysci                        City College of New York
dan@ccnysci.bitnet                 New York, NY 10031
                                   (212)690-6868