Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!malgudi!caen!spool.mu.edu!rex!ukma!aunro!alberta!ubc-cs!van-bc!skl
From: skl@wimsey.bc.ca (Samuel Lam)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: can a Bridge do null padding
Message-ID: <1991Jun21.085326.3584@wimsey.bc.ca>
Date: 21 Jun 91 08:53:26 GMT
Article-I.D.: wimsey.1991Jun21.085326.3584
References: <9106202109.aa00454@vaccine.worlds.COM>
Reply-To: skl@wimsey.bc.ca (Samuel Lam)
Organization: Balliffe Intersystem, Vancouver, B.C., Canada
Lines: 21

In article <9106202109.aa00454@vaccine.worlds.COM>, warren@worlds.com
 (Warren Burstein) wrote:
>I'm trying to get a uucp link working.  I am dialing from SCO Unix,
>thru a Telebit Trailblazer Plus, to a Microcom AX/2400 which talks to
>a Bridge, from there to a Decstation.  The protocol is failing, and it
>seems that the reason is that an octal 15 is getting a spurious NUL
>afterwards.  I have already disabled FCF and FCT.  Could the bridge be
>doing this padding?

It sounds like your "bridge" is really a terminal server (perhaps
made by a company named Bridge Communications).

The answer to your question is yes, it is very likely that your
terminal server is running as a Telnet client on that particular
serial port and is performing <CR> to <CR><NUL> mappings on the
inbound characters, assuming they are typed by a human user on
a terminal.

...Sam
-- 
<skl@wimsey.bc.ca>