Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!unmvax!ogicse!orstcs!guille!harish
From: harish@guille.ece.orst.edu (Harish Pillay)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: KA9Q query
Message-ID: <14285@orstcs.CS.ORST.EDU>
Date: 7 Dec 89 07:46:35 GMT
References: <14278@orstcs.CS.ORST.EDU> <18513@bellcore.bellcore.com>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: harish@guille.ECE.ORST.EDU (Harish Pillay)
Organization: Oregon State University, E&CE, Corvallis
Lines: 65

In article <18513@bellcore.bellcore.com> karn@ka9q.bellcore.com (Phil Karn) writes:
>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

Phil, thanks for your explanation.  I've got hold of the source code and I 
think I've got it figured out.  Telnetting into a machine running KA9Q 
works like a unix talk program. That's fine and I think it serves some good.
Actually, it might have been less misleading if it was labelled as a talk-like 
service (at least for the time being).  

I've also figured out how to:"net> telnet myhost" working.  It tooks a few
minutes of browsing through the code.  What is needed is a domain.txt file
in the root directory.  This file has contents such as follows (which was
created by pinging hosts after a domain server was added):

my domain.txt file contents
--------------------------------------------------------------
.	86400	IN	SOA	NIC.DDN.MIL.	HOSTMASTER.NIC.DDN.MIL.	891204	1800	300	604800	86400
guille.ece.orst.edu.	43200	IN	CNAME	ECE.ORST.EDU.
ECE.ORST.EDU.	43200	IN	A	128.193.48.1
nic.ddn.mil.	468772	IN	A	26.0.0.73
nic.ddn.mil.	468772	IN	A	10.0.0.51
.	468772	IN	NS	NIC.DDN.MIL.
.	468772	IN	NS	AOS.BRL.MIL.
.	468772	IN	NS	A.ISI.EDU.
.	468772	IN	NS	GUNTER-ADAM.AF.MIL.
.	468772	IN	NS	C.NYSER.NET.
.	468772	IN	NS	TERP.UMD.EDU.
.	468772	IN	NS	NS.NASA.GOV.
AOS.BRL.MIL.	499080	IN	A	128.20.1.2
AOS.BRL.MIL.	499080	IN	A	192.5.25.82
A.ISI.EDU.	468772	IN	A	26.3.0.103
GUNTER-ADAM.AF.MIL.	468772	IN	A	26.1.0.13
C.NYSER.NET.	468772	IN	A	192.33.4.12
TERP.UMD.EDU.	468772	IN	A	128.8.10.90
NS.NASA.GOV.	352376	IN	A	128.102.16.10
ECE.ORST.EDU.	43200	IN	SOA	ECE.ORST.EDU.	root.ECE.ORST.EDU.	50000327	21600	900	3600000	43200


I believe such a file is a standard one that is available on Unix boxes.
In my case, I pretty much bootstraped it.

-----
Harish Pillay                        harish@ece.orst.edu
Oregon State University