Path: utzoo!attcan!uunet!lll-winken!ames!rex!uflorida!mailrus!csd4.milw.wisc.edu!leah!rpi!rpi.edu!deven From: deven@pawl.rpi.edu (Deven Corzine) Newsgroups: comp.sys.amiga Subject: Re: Dnet2.0 Message-ID: Date: 12 May 89 10:06:24 GMT References: <6974@etana.tut.fi> <10260018@eecs.nwu.edu> Sender: usenet@rpi.edu Organization: RPI Public Access Workstation Lab, Troy NY Lines: 52 In-reply-to: gore@eecs.nwu.edu's message of 7 May 89 03:40:15 GMT In article <10260018@eecs.nwu.edu> gore@eecs.nwu.edu (Jacob Gore) writes: / comp.sys.amiga / deven@pawl.rpi.edu (Deven Corzine) / May 5, 1989 / >If this terminal server uses the >TELNET protocol, then you're shit outta luck. DNet will NOT run over >_telnet_, because even though the telnet protocol is a full 8-bit data >path, it isn't *quite* transparent enough. [lists possible problems] There is a telnet binary mode, and the terminal server may support it. True enough. I found that I could indeed force our telnet server into binary mode, and I am now running dnet (v1.1) over it. It's not an option that I recall being available in the software version which was running when I originally tried to figure it out... >The other major point of >nontransparency in telnet is the escape character, usually ^]. That's a function of the telnet user interface, not of the protocol itself. The terminal server may allow you to change it to another character, or disable it altogether. I understand it's a function of the UI, but the fact remains that ^] is a common escape character for telnet *programs* and it is a point of nontransparency, even though the protocol does not define it. On the Bridge CS/1 I'm using, the escape character ("ECMChar") is normally ^^, but is currently disabled. >On the other hand, the rlogin protocol IS transparent enough to run >dnet over. I'm surprised you haven't pointed out that "\n~", if followed by a command that rlogin recognizes (such as "^Z", ".", etc.), is an escape sequence, and needs to be disabled too (granted, it is less likely to occur in a random data stream, but...) The only reason I didn't point it out was I was getting tired of typing, the article was getting long enough as was, and it wasn't directly relevant. Yes, rlogin has "tilde escapes" which must be preceded with a newline. They are also disabled when the remote tty is put into raw mode, as dnet does, so it wasn't directly relevant. Technically, the tilde escapes are also a UI issue, but are also so fixed the distinction blurs, and is unimportant regardless. Purists. :-) Deven -- shadow@[128.113.10.2] Deven T. Corzine (518) 272-5847 shadow@[128.113.10.201] 2346 15th St. Pi-Rho America deven@rpitsmts.bitnet Troy, NY 12180-2306 <> "Simple things should be simple and complex things should be possible." - A.K.