Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!rutgers!bellcore!ka9q.bellcore.com!karn
From: karn@ka9q.bellcore.com (Phil Karn)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: KA9Q query
Message-ID: <18513@bellcore.bellcore.com>
Date: 7 Dec 89 04:30:56 GMT
References: <14278@orstcs.CS.ORST.EDU>
Sender: news@bellcore.bellcore.com
Reply-To: karn@ka9q.bellcore.com (Phil Karn)
Organization: Secular Humanists for No-Code
Lines: 22

In article <14278@orstcs.CS.ORST.EDU> harish@guille.ECE.ORST.EDU (Harish Pillay) writes:
>
>I've got PK's KA9Q running and am able to ftp into my machine and all.  
>Problem I have is in telnetting.  I get the connect message and all, 
>but nothing appears on the machine that I'm telnetting from.

It's not clear from your message, but if you're trying to telnet INTO
a machine running KA9Q, then what you see is exactly what should happen.
The telnet "server" in my code is not a real server; it simply creates a
telnet session on the remote machine so the two operators can chat in
real time (like UNIX "write").

I know, it's a bit of a crock, but the hams who use my package screamed for
it (keyboard chatting, as crude as it may be, is a common application for
amateur packet radio, and it is actually useful at times.) Anders Klemets
(klemets@sics.se) has hacked in a different Telnet server that actually
allows you to issue commands to NET over the network, but it's not complete
(you can't issue commands that create tasks, like sessions) and there's no
security. One of these days we'll do a "real" server, once I revamp the way
session output is done.

Phil