Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!uxc!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uxe.cso.uiuc.edu!krauskpf
From: krauskpf@uxe.cso.uiuc.edu
Newsgroups: comp.protocols.appletalk
Subject: Re: Problem with Telnet to Ultrix
Message-ID: <66000032@uxe.cso.uiuc.edu>
Date: 16 May 89 19:23:00 GMT
References: <11381@bloom-beacon.MIT.EDU>
Lines: 21
Nf-ID: #R:bloom-beacon.MIT.EDU:11381:uxe.cso.uiuc.edu:66000032:000:734
Nf-From: uxe.cso.uiuc.edu!krauskpf    May 16 14:23:00 1989




DEC's Ultrix system ships with IP trailers turned ON.

I admit it is a failing of NCSA Telnet to not handle trailers, even
passively, but I don't hear a lot of crying when they are turned off
either.  Performance gains, even for VAXen, have been debated on various
mailing lists before.

If NCSA Telnet hangs when talking to an Ultrix host when it should be
displaying a large page of text, you probably have trailers turned on
in the Ultrix system.  To turn them off, refer to the ifconfig man
page and include the -trailers option on the ifconfig line for your
boot sequence.

Tim Krauskopf
NCSA

yes, I do think we should eventually do something like Sun's "handle
anything" receiver which never sends, but can receive trailers.