🚀 go-pugleaf

From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Date: Sat, 22 Jun 91 23:15:26 EDT
Subject: GATEWAY/NETROM MBOX Problem


For the first time in awhile while I was at Field Day this afternoon I
logged into our TCP/IP switch with a standard TNC (no NOS) After getting
the openning banner I attempted a gateway connect and did not get a
connect - just a message telling it was attempting. I then entered the
escape character (^X default) and it immediately told me it was connected
followed be a disconnect. I experienced the same results with the netrom
connect. Only here I did not see a connect confirmation but I did an
'r' command. Nothing returned. When I did the escape I got the routes
back from the node and then a disconnect.

What appears to be happenning is that the circuit from the connection
to (me) the connecting ax25 station is not working. At least not until
the escape character is sent and then of course the circuit is broken.

This is with PA0GRI 0604 code. It is a recompile of the original. All
other aspects of the code appear to be functioning fine. Is anyone else
experiencing this?? It is simple to test. It does it thru nos as well.
'c ax0 noscall'.

I recall some talk of gateway problems recently but looking back it seems
that it may be unrelated.

Doug


----
From: mce@sdcc10.UCSD.EDU (Mark Edwards)
Date: Sat, 22 Jun 91 19:18:22 PDT
Subject: More DOS 5.0 & BC++


	Today I did some more polishing on the config.sys under DOS 5.0
to make it work nicely with Borland C++.  The final config will compile
the src0618.zip with no out of memory problems.  The current executable
is on thumper.bellcore.com in ~ftp/pub/ka9q/incoming/pop0618.exe.  Here
is the best config.sys to date:

files = 30
buffers = 20
stacks  0,0
SHELL=C:\DOS\COMMAND.COM C:\DOS\  /p /e:800
DEVICE=C:\DOS\HIMEM.SYS /shadowram:on
dos=umb
device=c:\dos\emm386.exe frame=e000 h=100 ram 1024
devicehigh=c:\dos\ramdrive.sys 1024 512 1024 /e
devicehigh=c:\dos\smartdrv.sys 1024
devicehigh=c:\lmouse\mouse.sys
devicehigh=c:\drivers\burndev.sys
devicehigh=c:\dos\ansi.sys
devicehigh=c:\net\netdev.sys
DEVICEhigh=C:\DOS\SETVER.EXE

	Placement of the frame=e000 was dictated by an ARCNET card using a
window at 0xd000.  I'm using the extended partition capability of DOS 5.0
rather than just one big partition  so that Xenix's DOS utilities can handle
the DOS partition.  Getting rid of the dmdrvr.bin that handled the d:
drive permitted use of the smartdrv.sys cache with Borland C++.  That cuts
the disk access substantially.
-- 
Mark C. Edwards             voice:      619/586-2204
Associate Systems Analyst   unix:       mce@pbsdts.pacbell.com
Matt 3:16-17,Acts 7:55-56,*John 8:17-18,*John 14:28,*Mark 13:32,
*John 20:17,*Matt 12:31-32,*John 17:20-23 (* Red letters) 


----
From: karn@thumper.bellcore.com (Phil R. Karn)
Date: Fri, 21 Jun 91 19:49:25 EDT
Subject: KA9Q QSYing to W6-land

I have recently decided to accept a position with Qualcomm, Inc, in
San Diego, California. My current target start date is August 1, 1991.
I will be working on their CDMA (Code Division Multiple Access, aka
"spread spectrum") cellular radio project. I am very much looking
forward to working with the guys at Qualcomm, many of whom are hams
(N6NKF, WT6G, KB5MU, WB6HHV, KA6IQA, just to name a few).

As I will be rather busy over the next month with all the many details
of moving cross country, expect me to be even less communicative on
this form than I've been lately.  However, I do plan on maintaining
some continuity in NOS and related efforts.  Sometime before I leave
Bellcore, I will move the /pub/ka9q hierarchy from
thumper.bellcore.com to ucsd.edu.  This will become the new canonical
collection/distribution point for NOS and related code. (Qualcomm is
on the Internet, but their link is only 56kb/s and I don't want all
that anonymous FTPing to bog down their link!)

I will announce on this list when I've made the switch. I'll replace
the old directory on thumper with a message redirecting people to
ucsd.edu. I already have an account on ucsd.edu that I will probably
use as a personal mail drop between the time I leave Bellcore and the
time I become established at Qualcomm. Mail forwarding from Bellcore
will probably be in place for a while, but of course using my new
address will be more efficient.  I'll let everybody know when this
happens, too.

Phil


----
From: Russ Nelson <nelson@sun.soe.clarkson.edu>
Date: Fri, 21 Jun 91 14:53:08 EDT
Subject: Re: DEPCA Ethernet From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)

   I suspect this DEPCA board is rather old. - 1988 or earlier

I believe that the Clarkson packet driver will not work on it.  I'd love
to have you fix it...


----
From: karn@thumper.bellcore.com (Phil R. Karn)
Date: Fri, 21 Jun 91 19:49:25 EDT
Subject: KA9Q QSYing to W6-land

I have recently decided to accept a position with Qualcomm, Inc, in
San Diego, California. My current target start date is August 1, 1991.
I will be working on their CDMA (Code Division Multiple Access, aka
"spread spectrum") cellular radio project. I am very much looking
forward to working with the guys at Qualcomm, many of whom are hams
(N6NKF, WT6G, KB5MU, WB6HHV, KA6IQA, just to name a few).

As I will be rather busy over the next month with all the many details
of moving cross country, expect me to be even less communicative on
this form than I've been lately.  However, I do plan on maintaining
some continuity in NOS and related efforts.  Sometime before I leave
Bellcore, I will move the /pub/ka9q hierarchy from
thumper.bellcore.com to ucsd.edu.  This will become the new canonical
collection/distribution point for NOS and related code. (Qualcomm is
on the Internet, but their link is only 56kb/s and I don't want all
that anonymous FTPing to bog down their link!)

I will announce on this list when I've made the switch. I'll replace
the old directory on thumper with a message redirecting people to
ucsd.edu. I already have an account on ucsd.edu that I will probably
use as a personal mail drop between the time I leave Bellcore and the
time I become established at Qualcomm. Mail forwarding from Bellcore
will probably be in place for a while, but of course using my new
address will be more efficient.  I'll let everybody know when this
happens, too.

Phil


----
From: dug@kd4nc.uucp (Doug Drye KD4NC)
Date: Sat, 22 Jun 1991 12:17:59 EDT
Subject: "Paying Duty"


I just received another set up PI cards today (thanks Doug, Kit on the
way when we finish them)
I didn't have to pay a cent... I expected to, but this is the second
shipment from them that didn't get taxed...

Geert, We do exactly what you suggested on the "value"
Only problem with declaring it as NO Value is that they
would not let me insure it ..!!!

doug

-- 
Doug Drye KD4NC


----
From: jrc@brainiac.mn.org (Jeffrey Comstock)
Date:  Sat, 22 Jun 1991 15:16:47 -0500
Subject: Re: KA9Q QSYing to W6-land

In article <9106212349.AA21850@epic.bellcore.com> you write:
>I have recently decided to accept a position with Qualcomm, Inc, in
>San Diego, California. My current target start date is August 1, 1991.
..
..

I used to live in San Diego.  It is a beautiful place, and alot warmer
than Minnesota.  Your going to love it.  When I lived there I went to
Minnesota for Christmas for a few weeks and it was about 10 deg above.
I got back to Cal about Jan 2 and it was 85 degrees.  One thing I really
loved was that even if it was 100 degree's, you go in the shade and it
is very comfortable. If it gets 100 here in Mn, it is very humid, so you
are like in a stew pot,  boiling no matter where you go.  I like to hang around
the meat department at Super Valu on days like that :-).

Anyway, no one probably told you this,  but you have to get some of those
surfer pants before you go out there.  They are the ones that go down to
about 1/4 of an inch above the knee, and are usually fluorescent green,
yellow, pink, purple, and black (all at the same time).  Make sure you preface
most comments with 'Hey duuuude' also.

:-)  :-)

Have a safe and happy QSY Phil.  Also, thanks for TCP/IP.  Now I am having
fun with it just to network computers locally, even if the RF is turned off.

Jeff


----
From: Anders.Klemets@cs.cmu.edu
Date: Mon, 24 Jun 91 05:42:40 -0400 (EDT)
Subject: AX.25 on top of IP

I have implemented Brians RFC-1226 for transmitting AX.25 frames over IP
in NOS. Apparently nobody else has done it for NOS yet? The code is
pretty simple since parts of it was already there. For instance, the
code for calculating the HDLC checksum was already in the file ppp.c.
(Although I am not perfectly sure that I am generating the right FCS.)

To make the AX.25/IP code more useful I also added a tiny piece of code
that implements crossband digipeating. 

Here is how to use it.
Suppose that I am running NOS with the callsign SK0WE-2 on the radio
interface. I want to setup a wormhole with w1xxx.foo.com. I will then
have to type:

	attach axip ai0 256 w1xxx.foo.com sk0we-3

where "ai0" is the name of my new 'wormhole' interface.
"256" is the MTU for AX.25.
"w1xxx.foo.com" is the hostname of my peer.
"sk0we-3" is an optional callsign of this new interface. The crossband
digipeating to my radio interface would not work if I did not specify a
callsign (other than sk0we-2.)

That is all. Assuming that w1xxx has done a corresponding setup, I can
now type
	connect ai0 w1zyx w1xxx-2
and the AX.25 frames will be sent to w1xxx.foo.com, where he will
digipeat them on the w1xxx-2 interface, which hopefully is the 2m port.

As long as both I and w1xxx use different callsigns on the radio and
wormhole ports crossband digipeating is supported.
One of the local TNC users will then be able to type
	Connect w1zyx Via sk0we-3, w1xxx-2

There is also a sequrity feature: The code will ignore AX.25 frames
received from IP hosts that have not previously been enabled with the
"attach axip" command.

The changed source files are available at thumper.bellcore.com as
pub/ka9q/incoming/axip.arc.

73, Anders


----
From: gvdg@cdc.com (Gerard Van Der Grinten)
Date: Mon, 24 Jun 91 7:31:39 CDT
Subject: Re: gateway problems

Hello All,
I uploaded nos_0605 again but whit a "small" mod in mailbox.c
It appeard that with the timer restructure a 240L was changed in 240*1000L
This was for the timer that flushes both sides of the gateway.
Just wait 8 minutes and you see your output.... ;-)
I changed it to 2 seconds (2*1000L) and all works normal.
calling every 240 ms looks a little overdone to me...
some other minor changes are also in.
Good luck, Gerard.
PS, it is on thumper in incoming untill moved and on wb3ffv and gvdgpc bbs.


----