Xref: utzoo comp.protocols.tcp-ip:6921 comp.dcom.lans:2731
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!munnari!murtoa.cs.mu.oz.au!charlie!kokab!jgm
From: jgm@kokab.cc.deakin.OZ (John Moorfoot)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans
Subject: Telnet problems with Bridge CS/1's
Message-ID: <7502@charlie.OZ>
Date: 26 Apr 89 07:38:09 GMT
Sender: root@charlie.OZ
Reply-To: jgm@kokab.cc.deakin.OZ ()
Organization: Deakin University, Computing Services
Lines: 13

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