Date: Thu, 30 Dec 93 04:30:01 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 #338
To: tcp-group-digest
TCP-Group Digest Thu, 30 Dec 93 Volume 93 : Issue 338
Today's Topics:
convers link
NOS 9600 baud problems
NOS and Network problem
Ohio TCP/IP address updates
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: Wed, 29 Dec 93 14:43:34 MST
From: kd6oat@kd6oat.ampr.org
Subject: convers link
To: TCP-Group@UCSD.Edu
The following concerns the 'convers link' behavior in jnos.
Condition:
When a convers link is established between my station and the local gateway,
the /w information is constantly updated even if no one is connected to the
conference area in my bbs.
Questions:
1. Is there a way to break a convers link once it has been established - other
than leaving nos ?
2. Is it possible to set up a time-out mechanism (similar to tdisc) such that
if there is no conference activity at my end for 't' period of time then the
convers link between my station and the gateway is broken ?
3. Is there a way to invoke convers link automatically when someone connects
to the conference in my bbs ?
Thanks for your reply.
73...Ken
------------------------------
Date: Wed, 29 Dec 93 09:25:10 CST
From: "John Martin" <martin@server.cdpa.state.ms.us>
Subject: NOS 9600 baud problems
To: Tcp-Group@ucsd.edu
Several hams here are using Net1itl version of NOS v890421.1i.tl. We all
like the split screen and have decided to use this version until we can
figure out JNOS. Everything works O.K. until we try FTP of a binary file
at 9600 baud. We are testing with a clear freq and a full scale signal.
The transfer starts O.K. but after a few packets it stops for a few
seconds to a few minutes.
Is anyone out there using this version of NOS at 9600 baud? Can you please
provide your autoexec.nos parms that are needed for 9600 baud?
Can anyone please describe the timers to me? I have no docs that describe
this version of NOS and it has two AX25 timers that I can't find docs on -
ax25 t1 and ax25 t2. Are ax25 t3 and ax25 t4 used the same as other nos
versions?
If you are using other versions of NOS at 9600 baud, I would also like
to know what type of setup was required to make it behave properly.
73 -- John
John Martin
MS Central Data Processing Authority
301 North Lamar St. Suite 508
Jackson, MS 39201-1495
(601) 359-2641
martin@server.cdpa.state.ms.us
------------------------------
Date: Wed, 29 Dec 1993 11:34:51 -0600 (CST)
From: csklf@knuth.mtsu.edu (Kelly L. Fulks)
Subject: NOS and Network problem
To: tcp-group@ucsd.edu
HELP!
I have a NOS gateway up that is running on the ethernet on one side and
rf on the other. The RF side works perfectly. On the ethernet side, I
can send email from the NOS box to the DEC and VAX stations just fine
and I can ftp a file off the NOS box to the DEC and VAX stations.
However, I can not send mail or files from the DEC and VAX stations to
the NOS box. I have watched the trace and the connection is made and a
few ether-packets get through but then it just stops. The box keeps
running just fine and continues to work but that process times-out. All
other functions seem to work just fine, I can telnet, AXIP, encap, etc.
just seems to effect computer to computer transfers.
Any help would be muchly appreciated.
73,
--
Kelly L. Fulks (KC4RDJ)
kc4rdj.ampr.org. [44.34.50.168]
kc4rdj@ab4zb.#midtn.tn.usa.na
csklf@knuth.mtsu.edu (internet)
US Mail 2507 Splinter Crt., Murfreesboro, TN 37130
------------------------------
Date: Thu, 30 Dec 93 05:58:54 UTC
From: Ron Atkinson <n8fow@wsu.n8fow.ampr.org>
Subject: Ohio TCP/IP address updates
To: tcp-group@ucsd.edu
I don't have the email address for the Ohio TCP/IP address coordinator, but
I believe it's N8EMR. Could I get your email address. A lot of Ohio's
addresses have changed (mainly Northwest Ohio) and your're updating the
ampraddr robot with the old invalid ip addresses. Plus an Ohio person is
now in Michigan with a Michigan address and the Ohio and Michigan addresses
keep deleting each other and getting tossed back and forth a lot on updates.
Ron N8FOW
Internet : ron@chaos.eng.wayne.edu
AMPRnet : n8fow@n8fow.ampr.org
#include <std_disclaimer.h>
/* all views and opinions expressed above are my own. */
------------------------------
End of TCP-Group Digest V93 #338
******************************
******************************