Path: utzoo!utgpu!jarvis.csri.toronto.edu!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: 6 May 89 02:55:39 GMT References: <6974@etana.tut.fi> Sender: usenet@rpi.edu Organization: RPI Public Access Workstation Lab, Troy NY Lines: 51 In-reply-to: mk59200@kaarne.tut.fi's message of 5 May 89 14:51:28 GMT In article <6974@etana.tut.fi> mk59200@kaarne.tut.fi (Kolkka Markku Olavi) writes: I can't get DNET working! Can someone out there help? Unix end: Sun 3/260, SunOS 4.0.1, Sun cc Amiga end: A500, KS1.2, WB1.3, ARP1.3, ConMan1.3, PopCLI3 The connection is through a TCP/IP terminal server, but I checked that it is 8bits, no parity. Yet, this could be your problem. 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. I believe the problem may be due to the fact that by definition the telnet protocol stream may NOT under any circumstances contain a single CR (0x0d) or a single LF (0x0a) in the data stream. The three choices are CR, NUL; LF, NULL; CR, LF. A plain CR or LF would be converted either to the character followed by a NUL (0x0a) [preferable] or to a CR, LF pair. The CR, LF pair is a generic EOL and will often (on Unix systems) be treated as a single LF. [Unix newline character] Unfortunately, this can leave you in a situation where you can not type a CR in the input stream. [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. Symptoms: I can connect and login to the Sun normally through the Dnet startup window, but when I try to start dnet, the Amiga side goes to a loop where it alternately opens and closes Fterm and Dnet windows, but nothing appears in them (except sometimes # or { characters) The # and { characters appear to be a sychronization phase in the dnet protocol. Anyhow, this sounds like a transparency problem... Matt, could you please consider an enhancement to optionally escape certain characters, etc. It would let a LOT of people use DNet who currently can't because they don't have a direct dialup... 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.