Date: Tue, 4 Jan 94 04:30:07 PST
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #343
To: tcp-group-digest
TCP-Group Digest Tue, 4 Jan 94 Volume 93 : Issue 343
Today's Topics:
JNOS Documentation
NNTP
NOS 9600 baud problems
Ottawa PI2 Card
Packet repeater interface logic
tnos-topics group (2 msgs)
tnos-topics update
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Mon, 03 Jan 1994 21:47:59 -0400 (EDT)
From: WG0B@delphi.com
Subject: JNOS Documentation
To: tcp-group@ucsd.edu
Also at ftp.ece.orst.edu in the JNOS40 subdirectory (I forget the path) is
the file set for JNOS40 v0.99 which includes a combined and somewhate
complete Commands Manual for JNOS and JNOS40. The document files will be
put up separately on the next release. They are in ascii text and Microsoft
Word (with stylesheet) formats.
If you want, the files are also on CyberGate BBS (316) 688-0915
14.4 kbaud, MNP5/V42.bis 8,n,1.
Doug Thompson, WG0B
co-author JNOS/JNOS40 Commands Manual and JNOS40 Users Guide
wg0b@delphi.com
------------------------------
Date: Mon, 03 Jan 1994 04:01:52 -0400 (EDT)
From: "Steve Dworkin, N2MDQ" <N2MDQ@delphi.com>
Subject: NNTP
To: tcp-group@ucsd.edu
Hello:
I am looking to get in contact with anyone successfully implementing
NNTP using MFNOS. Another station and myself are running with one
station configured as the server and the other as the client. At the
kick of the server, contact is made. A line passes with the word
NEWSGROUPS and the names of the groups with the date and time codes,
and then the response is four periods and a QUIT without any exchange
of postings. We have the 'nntp ihave' set to 2, but we think that we
may have missed a parameter somewhere, or don't have a directory set up
properly causing the server not to send the message list. Any help
in the way of a list of properly set parameters and a directory tree
would be appreciated.
73 de Steve, N2MDQ.
AmprNet: n2mdq@n2mdq [44.68.8.45]
Ax25 Packet: n2mdq@kc2fd.#nli.ny.usa.na
InterNet: n2mdq@delphi.com
------------------------------
Date: Mon, 3 Jan 94 12:56:28 CST
From: "John Martin" <martin@server.cdpa.state.ms.us>
Subject: NOS 9600 baud problems
To: mfoster@amoco.com
On Wed, 29 Dec 93 12:38:59 CST, Michael H. Foster wrote:
>
>John, I am curious where this Net1itl NOS comes from. Did you ftp
>it from a server somewhere? If so where? Any background will help.
>
>Does it have trace in it? How about the tcp view or tcp status?
>Some packets may be getting lost between the computer and tnc....
>
>mike, wa5txx
>mfoster@trc.amoco.com
I got nos1itl from another ham who downloaded it from a land line bbs (he
can't remember where). Maybe someone on the list will know where it is on
the internet. It has three windows. The top window is the trace window
(whenever trace is active). The middle window is the receive or command
responce window. The bottom window is the command window. Commands are
available to set the sizes of the windows.
One of the hams here who is using net1itl found a doc file for it that
is REAL CLOSE, so I will start with it.
We have played around with the timing and packet size parms and are
getting better throughput at 9600 baud, but it still goes to sleep
sometimes when FTPing.
------
_______
/ |
John W. Martin / | INTERNET:
Systems Programmer / | martin@server.cdpa.state.ms.us
Mississippi Central Data | C | oamartin@vm.cc.olemiss.edu
Processing Authority \ D | PACKET:
301 North Lamar Street | P | kb5ggo @ k5qne.ms.usa.na
301 Building, Suite 508 / A |
Jackson, MS 39201-1495 / | PHONE: (601) 359-2641
|______ | FAX: (601) 354-6016
/ |
\____|
------------------------------
Date: Mon, 3 Jan 94 14:39:46 WET
From: bm@hydra.carleton.CA (Barry McLarnon VE3JF)
Subject: Ottawa PI2 Card
To: nos-bbs@hydra.carleton.CA (NOS-BBS Mailing List)
Yes Virginia, there is an Ottawa PI2 card. I don't want to be accused of
"advertising" on the net (even though our group is non-commercial), so I
won't give any details here, but I don't think it's out of line to give a
pointer for more info. Send email (subject and text don't matter) to:
pi-info@hydra.carleton.ca
for details on the new rev of the Ottawa PI high-speed synchronous I/O card.
If you have a problem getting the info, or have further questions, try:
bm@hydra.carleton.ca
Happy Networking in '94 from the Ottawa gang...
Barry
--
Barry McLarnon VE3JF | Internet: bm@hydra.carleton.ca
Ottawa Amateur Radio Club | AMPRnet: barry@bbs.ve3jf.ampr.org
Packet Working Group | FreeNet: aa187@hydra.carleton.ca
------------------------------
Date: Mon, 3 Jan 1994 10:13:47 -0500 (EST)
From: "Barry McLarnon" <barry@dgbt.doc.ca>
Subject: Packet repeater interface logic
To: jra@lawdept.daytonoh.NCR.COM (Ackermann John)
> I'm putting together a revised version of the interface/controller for our
> full-duplex packet repeater. The goal is to directly tie the switch machine
> into the repeater, without using a radio.
>
> There are two data streams that could go the repeater transmitter -- the one
> from the receiver, and the one from the switch. A simple design would
> simply qualify each data stream with DCD or RTS as appropriate, and XOR them
> together. This would work fine as long as the receiver didn't open up while
> the switch was transmitting, or vice versa.
>
> But if both receiver DCD and switch RTS went active at once, the two data
> streams would mix and you'd get garbage. Of course, CSMA/CA should prevent
> this; when the switch has the transmitter, no one else would dare transmit.
> But we know that it doesn't always work this way.
>
> The question: is it worth it in the real world to either:
>
> a) give the switch priority (ie, when the switch is transmitting, lock out
> the receiver datastream), or
>
> b) come up with a latch that would work on a "first come, first served"
> basis, giving priority to whoever grabs the transmitter first. I can see
> potential race or deadly embrace problems with this, though.
>
> Any thoughts?
In our 56kb repeater, the switch controls what goes on the output. The data
streams from the repeater demod and from the switch go to a data selector,
and the rts line from the switch controls which input is selected. The
repeater output is keyed by the or'ed combination of the dcd from the repeater
demod and the switch rts line. Contention is managed by the switch sensing
the dcd. The switch has a smaller collision window than the other nodes on
the 56kb lan, so it is less likely to cause collisions. This arrangement has
worked extremely well for us.
I implemented the same strategy in a 1200bps repeater which uses the modem
in a TNC-2 for bit regeneration. The arrangement is similar to the one
described by NJ7P and N7OO in the 9th ARRL CNC (1990), but they allow the
dcd to control the data selector, which I think is a mistake... then any
dcd hits (falsing from noise or interference, transmissions from stations
that don't copy the repeater well, etc) while the switch is transmitting
will destroy the packet being transmitted.
Barry VE3JF
--
Barry McLarnon | Internet: barry@dgbt.doc.ca
Communications Research Center | AMPRnet: barry@bbs.ve3jf.ampr.org
Ottawa, Canada K2H 8S2 | PBBSnet: ve3jf@ve3jf.#eon.on.can
------------------------------
Date: Mon, 3 Jan 1994 07:39:48 -0800
From: brian@nothing.ucsd.edu (Brian Kantor)
Subject: tnos-topics group
To: tcp-group@ucsd.edu
In article <579@lantz.cftnet.com>:
>A reminder, as with all groups, if any special SMTP servers or MX
>records are needed to get mail to you, please supply these in a personal
>message to me so I can get your mail to you.
>
>I need this info for:
>
> segrest@bobseg.enet.dec.com
> samalott@sampc.cmhnet.org
That information is clearly available:
1# host -a sampc.cmhnet.org
The following answer is not authoritative:
sampc.cmhnet.org 85210 IN MX 10
mstar.morningstar.com
sampc.cmhnet.org 85210 IN MX 20
pun.cis.ohio-state.edu
For authoritative answers, see:
CMHNET.org 162087 IN NS VOLITANS.MORNINGSTAR.COM
CMHNET.org 162087 IN NS PUN.CIS.OHIO-STATE.EDU
Additional information:
pun.cis.ohio-state.edu 3110 IN A 128.146.56.1
VOLITANS.MORNINGSTAR.COM 121718 IN A 137.175.2.11
2# host -a bobseg.enet.dec.com
bobseg.enet.dec.com 7200 IN MX 0 us3rmc.bb.dec.com
bobseg.enet.dec.com 7200 IN MX 1 inet-gw-1.pa.dec.com
bobseg.enet.dec.com 7200 IN MX 2 crl.dec.com
bobseg.enet.dec.com 7200 IN MX 3 enet-gw.pa.dec.com
bobseg.enet.dec.com 7200 IN MX 4 inet-gw-2.pa.dec.com
Additional information:
us3rmc.bb.dec.com 609 IN A 16.52.80.3
inet-gw-1.pa.dec.com 86400 IN A 16.1.0.22
crl.dec.com 28800 IN A 192.58.206.2
enet-gw.pa.dec.com 86400 IN A 16.1.240.15
inet-gw-2.pa.dec.com 86400 IN A 16.1.0.23
Also, YOUR domain isn't registered properly; '.' is not a valid hostname.
1: host -a lantz.cftnet.com
The following answer is not authoritative:
lantz.cftnet.com 3265 IN SOA lantz.lantz.cftnet.com
postmaster.lantz.cftnet.com(
36233370 ;serial (version)
3600 ;refresh period
300 ;retry refresh this often
3600000 ;expiration period
3600 ;minimum TTL
)
lantz.cftnet.com 3265 IN NS lantz.lantz.cftnet.com
lantz.cftnet.com 3265 IN A 163.125.254.16
lantz.cftnet.com 451 IN MX 0 .
For authoritative answers, see:
lantz.CFTNET.COM 3265 IN NS lantz.lantz.cftnet.com
Additional information:
lantz.lantz.cftnet.com 3265 IN A 163.125.254.16
- Brian
------------------------------
Date: 3 Jan 1994 15:38:26 GMT
From: brian@nothing.ucsd.edu (Brian Kantor)
Subject: tnos-topics group
To: mail-tcp-group@ucsd.edu
id WAA10798 to <brian@nothing.UCSD.EDU>; Sun, 2 Jan 1994 22:10:10 -0800
Received: from wireless.nosc.mil by ucsd.edu; id WAA06315
sendmail 8.6.4/UCSD-2.2-sun via ESMTP
Sun, 2 Jan 1994 22:10:15 -0800 for <brian@ucsd.edu>
Received: from localhost (root@localhost) by wireless.nosc.mil (8.3/8.3) id WAA03222; Sun, 2 Jan 1994 22:13:41 -0800
Date: Sun, 2 Jan 1994 22:13:41 -0800
From: "Robert A. Buaas" <buaas@wireless.nosc.mil>
Message-Id: <199401030613.WAA03222@wireless.nosc.mil>
To: brian@ucsd.edu
Subject: schematic for TAPR DCD
Status: RO
Hi Brian--
I seem to have lost my copies of the schematic for the little board that
has only the DCD state machine, and an optional clock oc sc... H
osc... if you have one, can you fax it to me quick? 714/968-6781...
Depperation is setting in!!
Desperation (can you tell?)
thanks/bob
D
D
>From MAILER-DAEMON Mon Jan 3 15:33:15 1994
Received: from localhost by nothing.ucsd.edu (8.6.3/UCSDGENERIC.4)
id HAA12645 to brian; Mon, 3 Jan 1994 07:33:15 -0800
Date: Mon, 3 Jan 1994 07:33:15 -0800
From: MAILER-DAEMON (Mail Delivery Subsystem)
Subject: Returned mail: Host unknown (Name server: no data known for name)
Message-Id: <199401031533.HAA12645@nothing.ucsd.edu>
To: brian
The original message was received at Mon, 3 Jan 1994 07:33:13 -0800
from brian@localhost
----- The following addresses had delivery problems -----
brian@lantz.cftnet.COM (unrecoverable error)
----- Transcript of session follows -----
501 brian@lantz.cftnet.COM... 550 Host unknown (Name server: no data known for name)
----- Original message follows -----
Return-Path: <brian>
Received: from localhost by nothing.ucsd.edu (8.6.3/UCSDGENERIC.4)
id HAA12644 to ; Mon, 3 Jan 1994 07:33:13 -0800
Date: Mon, 3 Jan 1994 07:33:13 -0800
From: brian (Brian Kantor)
Message-Id: <199401031533.HAA12644@nothing.ucsd.edu>
To: tcp-group@ucsd.edu
Subject: Re: tnos-topics group
Newsgroups: mail.tcp-group
In-Reply-To: <579@lantz.cftnet.com>
Organization: The Avant-Garde of the Now, Ltd.
In article <579@lantz.cftnet.com> you write:
>A reminder, as with all groups, if any special SMTP servers or MX
>records are needed to get mail to you, please supply these in a personal
>message to me so I can get your mail to you.
>
>I need this info for:
>
> segrest@bobseg.enet.dec.com
> samalott@sampc.cmhnet.org
That information is clearly available:
1# host -a sampc.cmhnet.org
The following answer is not authoritative:
sampc.cmhnet.org 85210 IN MX 10
mstar.morningstar.com
sampc.cmhnet.org 85210 IN MX 20
pun.cis.ohio-state.edu
For authoritative answers, see:
CMHNET.org 162087 IN NS VOLITANS.MORNINGSTAR.COM
CMHNET.org 162087 IN NS PUN.CIS.OHIO-STATE.EDU
Additional information:
pun.cis.ohio-state.edu 3110 IN A 128.146.56.1
VOLITANS.MORNINGSTAR.COM 121718 IN A 137.175.2.11
2# host -a bobseg.enet.dec.com
bobseg.enet.dec.com 7200 IN MX 0 us3rmc.bb.dec.com
bobseg.enet.dec.com 7200 IN MX 1 inet-gw-1.pa.dec.com
bobseg.enet.dec.com 7200 IN MX 2 crl.dec.com
bobseg.enet.dec.com 7200 IN MX 3 enet-gw.pa.dec.com
bobseg.enet.dec.com 7200 IN MX 4 inet-gw-2.pa.dec.com
Additional information:
us3rmc.bb.dec.com 609 IN A 16.52.80.3
inet-gw-1.pa.dec.com 86400 IN A 16.1.0.22
crl.dec.com 28800 IN A 192.58.206.2
enet-gw.pa.dec.com 86400 IN A 16.1.240.15
inet-gw-2.pa.dec.com 86400 IN A 16.1.0.23
Also, YOUR domain isn't registered properly; '.' is not a valid hostname.
[ucsd brian] 1 : host -a lantz.cftnet.com
The following answer is not authoritative:
lantz.cftnet.com 3265 IN SOA lantz.lantz.cftnet.com
postmaster.lantz.cftnet.com(
36233370 ;serial (version)
3600 ;refresh period
300 ;retry refresh this often
3600000 ;expiration period
3600 ;minimum TTL
)
lantz.cftnet.com 3265 IN NS lantz.lantz.cftnet.com
lantz.cftnet.com 3265 IN A 163.125.254.16
lantz.cftnet.com 451 IN MX 0 .
For authoritative answers, see:
lantz.CFTNET.COM 3265 IN NS lantz.lantz.cftnet.com
Additional information:
lantz.lantz.cftnet.com 3265 IN A 163.125.254.16
- Brian
------------------------------
Date: Mon, 03 Jan 94 09:20:44 EST
From: brian@lantz.cftnet.com
Subject: tnos-topics update
To: tcp-group@ucsd.edu
Message-Id: 674_lantz
From: brian@ko4ks.#tpa.fl.usa.na
To: tcp-greoup@ucsd.edu
Sorry to have to use these other groups like this, but this is the only
avenue I can think of.....
The following two stations need to send me a personal message, so I can
determine a MX record from their routing:
ron@chaos.eng.wayne.edu
mwestfal@csci.csusb.edu
Also, for everyone's info.....
If you subscribe to the group and do NOT get back a response in a while,
don't send a second request.... Send me a personal message. Most probably
the request got here, and my routing wasn't complete enough (yet) to
get it back to you. The personal message will give me more info for that.
Once again, sorry to send through the group!
/----------------------------------------------/
/ Brian A. Lantz/KO4KS /
/ /
/ Packet: KO4KS@KO4KS.#TPAFL.FL.USA.NA /
/ Internet: brian@lantz.cftnet.com /
/ Live long, and prosper! /
/----------------------------------------------/
------------------------------
End of TCP-Group Digest V93 #343
******************************
******************************