Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!kth!draken!tut!ra!vinsci
From: vinsci@ra.abo.fi (Leonard Norrg}rd DC)
Newsgroups: comp.sys.amiga
Subject: Re: Dnet2.0
Summary: DNetting possible over telnet using Bridge Comm's CS200 servers
Message-ID: <120@ra.abo.fi>
Date: 7 May 89 12:10:29 GMT
References: <8905070127.AA13702@postgres.Berkeley.EDU>
Organization: Abo Academy, Finland
Lines: 64

dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) wrote:
>:[Can be nasty telnetting out.]  Anyhow, I digress.  DNet will not run
>:over telnet, probably because of this point of non-transparency.
>:Unless Matt has specifically changed it for 2.0 [I haven't tried it
>:yet] but I don't think so.  [Matt?]  The other major point of
>:nontransparency in telnet is the escape character, usually ^].  (don't
>:know the character code offhand.)
>:
>:On the other hand, the rlogin protocol IS transparent enough to run
>:dnet over.  If you can use a straight TCP connection or an rlogin
>:connection (which is fairly close) DNet should run fine over it.  With
>:a telnet connection, you can't do much about it.
>
>	DNet will not run under telnet for that and other reasons... like
>^] causes an escape.  DNet *will* run under rlogin because rlogin recognizes
>when a terminal is placed in RAW mode and turns off it's escapes.

  I had the same problem when I first started using DNet, ie. the terminal
servers the modems are connected to didn't have a binary line as default.
Our servers are Bridge Communications CS200 with 10 ports, running Bridge's
TCP/IP software. After some experimenting and RTFM:ing I found out that it
was indeed possible to get a binary path over telnet with these servers.
It's somewhat of a kludge, but it works: Since you can't set the telnet session
parameters before you actually have a session, you need to escape to the
server and change the parameters to binary after you login but before you start
DNet. So, the CS200 command looks like this:

     set fct=none fcf=none ecmchar=disabled xmitbinary=on

  This disables flowcontrol (usually xon/xoff), disables the telnet escape
character and finally leaves any combination of CR/LF alone.
  Appended is the output from a "SHOW PARAMETERS" on the CS200 with the
above command executed (the "do binary" executes a macro which contains the
above command).
  Of course, this won't help if your server is of some other type...

--
Leonard Norrgard, vinsci@abo.fi, vinsci@finabo.bitnet, +358-21-654474, EET.

-----$(SCISSORS)--------------$(SCISSORS)------------$(SCISSORS)-------------
(!3) ASAc.110>> do binary
(!3) ASAc.110>> sh para
Parameters  for PortId !3, current session
...................Port Transmission and VTP Characteristics...................
BUffersize = 82     DeVice = ( Terminal, Glass, DeFault )
InterAction = ( Verbose, Echo, NoMacroEcho, MacroBreak, BroadcastON, NoLFInsert )
InitMacro = ""      MaxSessions = 3     PRIvilege = GlobalNM
.........................Port Physical Characteristics.........................
BAud = 9600         BSPad = None        CRPad = None        FFPad = None
LFPad = None        TabPad = None       DataBits = 8        DUplex = Full
LinePRotocol = ASynchronous             PARIty = ( None )   StopBits = 1
UseDCDout = ( AlwaysAssert, NoToggle )  UseDTRin = Ignore
.................Session Transmission and VTP Characteristics..................
BReakAction = ( InBand )                BReakChar = Disabled
DIsconnectAction = None                 DataForward = None  ECHOData = OFF
ECHOMask = ( AlphaNum, CR, Term, Punct )                    ECMChar = Disabled
NetAScii = UseLF    FlowControlFrom = None
FlowControlTo = None                    FlushVC = OFF       IdleTimer = 2
LongBReakAction = ( Listen, OutofBand ) LFInsertion = None  MOde = Transparent
XmitBinary = ( ON )
..................Session & User Interface Editing parameters..................
ERAse = ^?          LineERAse = ^U
LocalEDiting = ( NoDataEditing, CmdEditing )                ReprintLine = ^R
VERBatim = Disabled WordERAse = ^W